Not started project with bad mount
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
To Reproduce
- Create github docker app
- Deploy
- Add broken mount
- 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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the deployment on Dokploy 0.26.5 with a broken mount on the same server, then trace why deployment succeeds while the container does not start. Done means the deployment reports the broken mount with a useful error instead of claiming success, and the failure is visible in logs or errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 54/100