My app doesn't start anymore and there's 5-6 containers hanging around.
It worked normal before last deployment (just one string change) which triggered a new deployment, and it got stuck. Tried to clean cache, stop, rebuild, push a new one. It simply doesn't start anymore, and there's only logs in one or two of the containers (see screenshot) - rest are empty. I'm using Dokploy Cloud - thanks! 😄
12 Replies
restarted my VPS and that didn't help either
Looks like a health check that is failing
yeah it looks like it keeps trying to spawn a container, then it disappear
didn't change anything tho, werid
got an idea how I can fix it?
Do you have any health checks running? Either in the Dockerfile or the compose or somewhere related to that project.
nope
normal railpack setup
runs normal locally, like I said; it worked completely fine until now :/
everything else runs smooth, no idea what happened
Without logs from the application, which I see is hard to obtain due to rolling crashes it's not much for me to go on to help
yeah, any way to figure out which container is the newest one? and I guess no way to kill all containers?
i feel like dokploy got stuck somehow, i commented everything out, and deployed only this line
same issue
issue is all the containers are in state "created" I guess, and none of them exit like they are supposed to
if you have no other idea I guess I can try creating a new project
stopping the app killed some of the containers, two are left in created state tho
One thing is what dokploy is reporting, but try to verify from the terminal with
docker ps and docker service ls how many are actually running when you stop the service in Dokploysend you a dm
@Siumauricio solved it, thanks! 🙂