mbentley

Get container logs using: docker logs omada-controller >& output.log And mongodb logs using: docker cp omada-controller:/opt/tplink/EAPController/logs/mongod.log mongod.log Replace the container name if it is not omada-controller.

Sorry, I missed the notification on this. Based on these volume paths, you did not specify a volume name. You can either use Docker managed volumes where you provide the persistent data path a name or you can use a bind mount. The image is configured to automatically create a volume but if you do not specify a name, it will create one with a random guid. In this case, your data is in the volume `a13fa10908be8af6443af13b1d41a1a8ffa0fbd1f9fa8e98224ae985e83e679d` and your logs are in `9038ba554ee7b24e19c77106f41be5313d61031dff1c5d6ba64e149a24dc1a3f` for this instance of your controller. You probably have other volumes that show with `docker volume ls` but you won't be able to tell what is what without manually inspecting the contents in `/var/lib/docker/volumes/<volume_guid>/_data`.

Sorry, I was assuming you understood that `omada-controller` was the name of your controller and you only paste this part: docker inspect --format '{{json .Mounts}}' <controller-name>

If you don't know where the container is mounted the data, you can use docker inspect to find out: This just lists the mounts: # docker inspect omada-controller | jq '.[]|.Mounts' [ { "Type": "bind", "Source": "/zfs/apps/omada-controller/cert", "Destination": "/cert", "Mode": "", "RW": false, "Propagation": "rprivate" }, { "Type": "bind", "Source": "/zfs/apps/omada-controller/data", "Destination": "/opt/tplink/EAPController/data", "Mode": "", "RW": true, "Propagation": "rprivate" }, { "Type": "bind", "Source": "/zfs/apps/omada-controller/logs", "Destination": "/opt/tplink/EAPController/logs", "Mode": "", "RW": true, "Propagation": "rprivate" } ] Or if you don't have jq: # docker inspect --format '{{json .Mounts}}' omada-controller [{"Type":"bind","Source":"/zfs/apps/omada-controller/data","Destination":"/opt/tplink/EAPController/data","Mode":"","RW":true,"Propagation":"rprivate"},{"Type":"bind","Source":"/zfs/apps/omada-controller/logs","Destination":"/opt/tplink/EAPController/logs","Mode":"","RW":true,"Propagation":"rprivate"},{"Type":"bind","Source":"/zfs/apps/omada-controller/cert","Destination":"/cert","Mode":"","RW":false,"Propagation":"rprivate"}]

Sounds like you did not map your persistent data to a volume or a bind mounted location.

Sorry about that - an issue with a new experimental feature to allow users to make the MongoDB work from another container or host accidentally broke the connection to the MongoDB that the controller spins up. I forgot to add a default connection string but it should be fixed now.

You’re out of disk space wherever it is trying to write to. Errors specifically call that out.

Yes, others are reporting the same. I created an issue on the TP-Link forums: https://community.tp-link.com/en/business/forum/topic/623942?replyId=1258164 and there is a discussion tracking it on the image GitHub: https://github.com/mbentley/docker-omada-controller/issues/342. People are also posting about it on Reddit: https://www.reddit.com/r/TPLink_Omada/comments/16rb07h/admin_login_doesnt_work_after_updating_to_latest/ It doesn't seem to be happening to everyone though so that's the odd part.

I would suggest posting to the TP-Link support forums since this isn't a massive group of experts on the software itself.

I am not as familiar with the interface for starting a container but just make sure that the ports exposed AND the environment variables that you used to launch the container match. If you have previously launched the container with different ports, you can't just change them due to how the controller software is written. Take a look at this part of the readme if you want to fully understand but the env vars modify a properties file which is only read on the very first startup by default.

Hey all - I'm the Docker image author. If people are having specific issues with the image not running or unexpected errors, I can help but would appreciate issues being posted to GitHub. @hedrinbc - No idea where or how the container image is published to the marketplace but there may be an update needed to change how the container is run as it looks like some people are hitting ulimits as you can see here: https://github.com/mbentley/docker-omada-controller/issues/298#issuecomment-1491937963 This would be a change to how the run command is defined assuming it uses docker run type parameters.