Docker / Docker
Docker Compose Watch Fails: Error Response from Daemon Cannot Overwrite Non-Directory
Developer uses docker compose up --watch for hot-reload but encounters daemon-level copy errors when file/directory state conflicts occur Includes evidence for Docker troubleshooting demand.
- Category
- Docker
- Error signature
docker compose up --watch: copying files: Error response from daemon: cannot overwrite non-directory- Quick fix
- Compare the failing environment with a known working setup, then change one configuration value at a time.
- Updated
What this error means
docker compose up --watch: copying files: Error response from daemon: cannot overwrite non-directory is a Docker failure pattern reported for developers trying to developer uses docker compose up —watch for hot-reload but encounters daemon-level copy errors when file/directory state conflicts occur. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.
Why this happens
Found on GitHub docker/compose issues (#13795, reported 2 days ago). Specific Docker Compose watch mode bug with concrete error message and daemon interaction. Recent report indicates active issue. Category: Docker per mapping rules.
Common causes
- Found on GitHub docker/compose issues (#13795, reported 2 days ago). Specific Docker Compose watch mode bug with concrete error message and daemon interaction. Recent report indicates active issue. Category: Docker per mapping rules.
Quick fixes
- Confirm the exact error signature matches
docker compose up --watch: copying files: Error response from daemon: cannot overwrite non-directory. - Check the Docker account, local tool state, and provider configuration involved in the failing workflow.
- Compare the failing environment with a known working setup, then change one configuration value at a time.
Platform/tool-specific checks
- Verify the command, editor, extension, or API client that produced the error.
- Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
- Avoid deleting credentials, local model data, or project settings until the failing scope is clear.
Step-by-step troubleshooting
- Capture the exact error message and the command, editor action, or request that triggered it.
- Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
- Review the source evidence below and compare it with your environment.
- Apply one change at a time and rerun the smallest failing action.
- Keep the working fix documented for the team or deployment environment.
How to prevent it
- Keep provider/tool configuration documented.
- Record non-secret diagnostics such as tool version, provider name, model name, and command path.
- Add a lightweight check before CI or production workflows depend on the tool.
Sources checked
Evidence note: Found on GitHub docker/compose issues (#13795, reported 2 days ago). Specific Docker Compose watch mode bug with concrete error message and daemon interaction. Recent report indicates active issue. Category: Docker per mapping rules.
Related errors
- Docker
FAQ
What should I check first?
Start with the exact docker compose up --watch: copying files: Error response from daemon: cannot overwrite non-directory text and the smallest action that reproduces it.
Can I ignore this error?
No. Treat it as a failed Docker workflow until the root cause is understood.
Is this guaranteed to have one fix?
No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.
How do I know the fix worked?
Rerun the same command, editor action, or request. The fix is working when that action completes without docker compose up --watch: copying files: Error response from daemon: cannot overwrite non-directory.