Deploy fails with "No such container: select-a-container" after Nixpacks build completes

[ShaonPro]

To Reproduce

select-a-container error during normal Deploy (not Open Terminal), right after Nixpacks build completes, for Application (Nixpacks) deployments.

Current vs. Expected behavior

Current behavior

• Click Deploy on an Application (Nixpacks).
• Build completes successfully (Nixpacks build completed).
• Deployment fails with: Error response from daemon: No such container: select-a-container
• No Swarm service is created; the app never runs.

Expected behavior

• Click Deploy on an Application (Nixpacks).
• Build completes successfully.
• Dokploy creates the Swarm service using the correct container/service name (e.g. mern-drivlex-3j6zc6).
• The app starts and is reachable via its domain.

Provide environment information

Operating System:
   OS: Ubuntu 22.04 LTS
   Kernel: 6.8.0-100-generic

Dokploy version: 0.27.1

Which area(s) are affected? (Select all that apply)

Docker Compose, Application, Docker

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

Yes

[Siumauricio]

Hey, I tested and works fine, make sure you don't have other configurations otherwise it can be something like this https://docs.dokploy.com/docs/core/troubleshooting#mounts-are-causing-my-application-not-to-run

[ShaonPro]

I did the same with many applications, but unfortunately, I was facing the same issues. Maybe due to many applications and NixPack issues.

[Siumauricio]

I did the same with many applications, but unfortunately, I was facing the same issues. Maybe due to many applications and NixPack issues.

Add a simple repo to deploy with nixpacks to test it, I see nobody has reported the same issue so very probably a misconfiguration from your side

[tr1fled]

I have the same exact issue, with the output being:

...
#16 DONE 6.4s
=== Successfully Built! ===
Run:
docker run -it CENSORED
✅ Nixpacks build completed.

when you run the command in the host machine, it starts the docker container as normal, and when daemonized it shows up in the Docker tab. it is extremely annoying to have to do this after every deploy, this initially happened to me in another Dokploy "project", the solution was to erase the project and remake it.

[Siumauricio]

I will close this; issues without a valid reproduction will be closed.