Unable to run a container

[mipruch]

I have no problem building the app. It is a simple "Hello world" Nuxt app (node) pulled from my GitHub. Left as is, it should natively runs on port 3000.

After the deployment is done with successful log:

the app is not running.

I'm using the default Nitpicks setting, no custom Dockerfile.

I can see the image being made using "docker images", but "docker ps -a" shows no new container.

Also, I'm unable to see the logs for the app as no container is running.
It only shows:
Error response from daemon: No such container: select-a-container

If I click on the Reload button, nothing happens and the spinner won't stop spinning...
If I run the image manually using "docker run -p 3010:3000 test-nuxt-pew2aa", the app runs correctly...

Any help? Thanks.

[Siumauricio]

When the error is not shown anywhere, there can be several reasons, to see the errors in more detail you can go to /dashboard/swarm and see the services there you should see the error in more detail.

you probably added some invalid volume, some already busy port or something else that is preventing docker from starting the container.

[mipruch]

It might be the port issue. I've completely reinstalled docker and dokploy and I'm keep getting the error. I port forward 3004 to 3000 and the 3004 port is free for sure. If I run the image manually with that port forwarding, it works fine.

Any ideas why the Swarm throws this error? I don't use any volume mounting.

[Siumauricio]

Can you enter to your server and run docker --version?

Looks like this bug was introduced in a 27.0.2 version moby/moby#48069

[mipruch]

It says Docker version 27.4.1, build b9d17ea.
Thanks for the link, I'll check it. What I don't quite understand is that if I create a clean EC2 instance and do exactly same steps, it works fine. But not on my local linux server.

[Siumauricio]

Is strongly recommended to install dokploy on a fresh machine to prevent kind of that issues

[mipruch]

I'm getting the same error even with Docker version 26. I'll try reinstalling linux next.