dify - 💡(How to fix) Fix Bug: API container logs Gunicorn control socket permission error

Self Checks

• I have read the Contributing Guide and Language Policy.
• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report, otherwise it will be closed.
• 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.14.2

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

• Build and start the API container as the non-root dify user.
• Use Gunicorn 26, which enables the control socket by default.
• Inspect the API container startup logs.

The container runs with:

uid=1001(dify)
HOME=/home/dify

But /home/dify is not created as a writable directory in the image.

✔️ Expected Behavior

• The API container starts without control socket permission errors.
• The dify user has a valid writable home directory for runtime files.

❌ Actual Behavior

Startup logs include:

Control server error: [Errno 13] Permission denied: '/home/dify'

Gunicorn continues to boot workers, but the error is noisy and can also affect other libraries that write cache, socket, or state files under $HOME.