
CloudCMD with container does not start
-
- OMV 5.x
- resolved
- mbinax
-
-
mbinax
Changed the title of the thread from “CloudCMD container does not start any more” to “CloudCMD with container does not start”. -
since months but now it always fails to start, getting this kind of error
I stopped using this due to issues with updates, you have another post here does ouroboros control CloudCMD. Do you deploy your containers using stacks or do you manually create them.
-
I used stack to deploy it
-
-
it looks like the dockerfile of cloudcmd had a missnamed entrypoint, thats the reasen the file (cloudcmd.js) could not found during startup.
Remove the image and pull a fresh one.
-
I used stack to deploy it
One way I resolved this was to use a specific tag as I deployed using stacks, there was quite a lengthy back and forth on his github page until it was resolved, but instead of using the tag :latest I found a tag that worked without errors. But since moving to OMV5 I've stopped using it.
-
Solved...
I did a backup of the stack by duplicating it... and this one it works fine!
-
-
mbinax
Added the Label resolved
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!