Skidmark

Is /mnt/disks/extrassd/docker-settings/omada-controller the expected location for the container to use? At least on my machine, that directory wouldn't persist after a reboot.

Hi, I didn't see any replies to your question so I thought i'd share what I found. I had the same issue and I believe I figured out what it was. The container's default path for it's data, logs, etc begins with "/mnt/disks". in unraid this directory doesn't exist but when the container runs, it creates it. The directory works fine until a host reboot occurs at which point the directory will cease to exist hence the first run experience upon logging in after a reboot. I fixed it by copying the contents of the default path to unraid's appdata and mapping the container paths to appdata (/mnt/user/appdata/omada-controller) as opposed to the container default (/mnt/disks/extrassd/docker-settings/omada-controller). Anywho, hope that helps.