Hi Ben,
First of all, thanks very much for voluntarily maintaining an UnRAID compatible docker for mbentley's TP-Link Omada SDN controller. I wanted to make a quick suggestion from a software usability standpoint that I think is a low-effort way to avoid a lot of future headaches for users of your docker.
As you probably know, many, if not most UnRAID dockers are preconfigured with host file paths that do not require careful manual entry, so UnRAID users have been "trained" to expect this behavior when installing a new docker. Your defaults on host paths, if left unchanged, produce behavior that is sort of the worst of both worlds - it appears to work normally, but in fact UnRAID creates a temporary path based on your hard-coded personal server settings with "extrassd" that does not persist after reboot, causing in some cases hours and days of confusion for users of this docker.
To resolve this situation, I would recommend one of the following minor adjustments to the docker:
1) Set the default host paths to the following:
/mnt/user/appdata/omada-controller/data/
/mnt/user/appdata/omada-controller/work/
/mnt/user/appdata/omada-controller/logs/
This solution would I believe clear up a lot of user frustration and confusion after they just accepted your default (personal) host paths of your "extrassd." Many / most UnRAID users opt to use a Cache drive and map the /appdata share exclusively to that drive, so it would not be stored on spinning drives with parity. If for some reason you believe this solution might create an issue (I believe you referenced file permissions "on the array"), please let me know. I assume UnRAID would create these directories if they do not yet exist in the appdata share. This could also be hard-coded into mnt/cache/appdata/ I suppose, but I'm not certain why that would be a more optimal solution.
2) Another solution could be to make a much more prominent note in the Docker Template settings themselves (via instructional text below the host paths and/or in the blue description text], the Community Apps description and/or this support thread that explicitly states that it is MANDATORY for the user to reset these host paths to fit their own system needs. However, I believe that if you make the changes in my suggestion above, these instructions may be unnecessary.
Finally, someone (not me) has produced a YouTube video walking users through installation of your Docker, and you may wish to link to this video in the first posts of this support thread for future reference [note that this person manually creates folders in /mnt/cache/appdata (which I did not think was necessary) and then edits the default host paths]:
I believe these changes could cut down on demands on your time as well as a lot of user frustration in this thread, on Reddit, and elsewhere.
I hope these suggestions may be helpful and again, huge thanks to you @hedrinbc and @mbentley for supporting this useful docker.
Cheers.
