cp: -r not specified; omitting directory '/docker-entrypoint-mount.sh

[Adong17777]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

After running the docker compose up -d command, the page fails to open, and the container log shows:
cp: -r not specified; omitting directory '/docker-entrypoint-mount.sh'

2. Additional context or comments

No response

[dosubot[bot]]

Hi @Adong17777! I'm Dosu and I’m helping the dify team.

This error happens because the container's entrypoint script tries to copy /docker-entrypoint-mount.sh as a file, but it's actually mounted as a directory, and the cp command is missing the -r flag for recursive copy. This prevents the application from starting since the script isn't copied or executed as intended.

To fix it, check your docker-compose.yaml and make sure /docker-entrypoint-mount.sh is mounted as a file, not a directory. If you're customizing the entrypoint, ensure the cp command matches the type—use cp -r if it's a directory, but typically this should be a file. If you're using the default Dify setup, remove any custom mounts or overrides that introduce this error. More details and examples are discussed in this issue.

If the problem persists, also check for port conflicts, unhealthy containers, or permission issues, as these can cause similar startup failures, but they won't resolve the cp error itself.

To reply, just mention @dosu.

---

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