Not started project with bad mount

[ariran5]

To Reproduce

1. Create github docker app
2. Deploy
3. Add broken mount
4. Click deploy, deploy success and container not started. No logs, no errors

Current vs. Expected behavior

Current:
Click deploy, deploy success and container not started. No logs, no errors

Expected:
Click deploy, deploy success and container not started. Error messages about broken deploy

Provide environment information

Dokploy 0.26.5

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

Application

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?

No

[dosubot]

Hi @ariran5! I'm Dosu and I’m helping the dokploy team.

This is a known limitation in Dokploy's deployment pipeline. The deployment is marked as "done" immediately after the Docker Swarm service is created/updated, without verifying that containers actually start successfully .

When a broken mount is configured, the Docker service creation succeeds (so deployment shows "success"), but the container fails to start due to the invalid mount. Since Dokploy doesn't poll container health post-deployment, this failure goes undetected .

Workaround: You can check actual container status manually with:

docker service ps --no-trunc <service-name>

This behavior has been reported in other contexts as well—users have noted that when containers fail health checks and Docker Swarm rolls them back, the UI still shows success .

The codebase does have functions for inspecting container state , but they're not currently integrated into the deployment verification flow. This would be a good area for improvement if someone wants to contribute a fix.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}