5.14.x - Controller will randomly not start due to Unsatisfied dependency / Circular Reference
This was reported on my repo for the container image I build. This is happening for both the beta and GA versions of 5.14.x: both of the latest beta versions, 5.14.0.11 and 5.14.20.9 and the 5.14.26.1 GA version. There are reports of the app not starting. Oddly enough, it's a scenario where you can take the same Docker image, run it on two identical machines (same OS, same kernel, same Docker version) and get two different results. One will run it fine, the other won't. This is a brand new, clean installation with no previous controller configuration data. I will try to post the logs as a follow up but it keeps saying I am posting an "illegal link" in my post for some reason - probably something in the text of the post.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
i posted a thread on reddit in case we have more people with issue but hadn't yet reported here in the tplink forum, because they hang out on reddit instead
https://www.reddit.com/r/TPLink_Omada/comments/1e64bld/docker_omada_controller_514x_beta_ga_does_not/
- Copy Link
- Report Inappropriate Content
Another data point.
I encountered this issue when attempting to deploy on a fresh install of Ubuntu 24.04-LTS. Same thing on two different servers, a low-end server (Atom CPU C3758R) and a fairly hefty server with 24 cores.
I was able to get it to work after switching to a fresh install of Debian 12.6.
All attempts were on bare metal.
- Copy Link
- Report Inappropriate Content
Works on the same hardware as just above on Ubuntu 22.04-LTS.
- Copy Link
- Report Inappropriate Content
I am running 22.04-LTS with different hardware but run into the issue.
- Copy Link
- Report Inappropriate Content
I'm new in docker topic. I use a raspberry with Portainer and updated to the new version.
Now the container is in a boot loop. How can I downgrade it that it works properly again. I never done a backup by hand and I hope after downgrade my configuration is working again
How to downgrade step by step pls.....
Thanks very much
- Copy Link
- Report Inappropriate Content
@_Moogwai_ - check out my instructions in this thread over on the GitHub issue: https://github.com/mbentley/docker-omada-controller/issues/418#issuecomment-2223732459
- Copy Link
- Report Inappropriate Content
If there is anyone that is truly stuck and couldn't roll back or wants to use the beta, there is now an updated beta version (it's beta so like TP-Link says, use it at your own risk) of the containerized image. See this post for more info: https://github.com/mbentley/docker-omada-controller/issues/418#issuecomment-2252611594
Just be warned that the beta could break anything at any time and may not upgrade successfully so having backups is a must.
- Copy Link
- Report Inappropriate Content
@mbentley sounds like promising news. Have TP-Link indicated when the fix is likely to be generally available please?
Thanks!
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Fae - any idea when the next non-beta version is scheduled to come out? It's been a while since the last beta. I'm still getting people filing issues on my GitHub repo having problems. It's at 44 participants and 100 comments right now.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 17
Views: 5368
Replies: 43
Voters 4
