[Help]: exec /entrypoint.sh: no such file or directory #643
-
Controller Versionv5 Describe Your Issue or QuestionI recently launched the Omada Controller in a container on a Synology NAS DS925+. Expected BehaviorJust run Steps to ReproduceRun it How You're Launching the ContainerContainer LogsMongoDB LogsNo response Additional ContextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 9 replies
-
|
So are you building the image from the cloned repo or pulling from Docker Hub? I am running the latest image just fine. Could you do a docker compose pull and then try to run the container again? |
Beta Was this translation helpful? Give feedback.
-
|
The image is downloaded from Docker hub |
Beta Was this translation helpful? Give feedback.
-
|
Are you directly deploying it with compose or are you using Portainer or Synology Container Manager directly? I've seen other issues where the entrypoint or CMD have weird configurations or they're misinterpreting them. You can always to just try a very simple |
Beta Was this translation helpful? Give feedback.
-
|
Screenshots from the Synology GUI
|
Beta Was this translation helpful? Give feedback.
-
|
You pointed me to the possibility that Container Manager might be malfunctioning. I removed the package, along with the images and containers, and reinstalled it, and it works. I don't know what happened. |
Beta Was this translation helpful? Give feedback.





You pointed me to the possibility that Container Manager might be malfunctioning. I removed the package, along with the images and containers, and reinstalled it, and it works. I don't know what happened.
Thank you so much for your help!