docker-init_permissions-1 Exited

[imxiaopin]

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.11.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

docker-init_permissions-1 Exited

log: Permissions already initialized. Exiting. I have strictly upgraded according to the upgrade requirements for each version on the official website, and checked and ensured that the .env file is up to date, including the 1.10.1's # Update directory ownership on the host sudo chown -R 1001:1001 ./volumes/app/storage

✔️ Expected Behavior

It should start normally

❌ Actual Behavior

No response

[dosubot]

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

The exit of the docker-init_permissions-1 container with the message "Permissions already initialized. Exiting." is normal and expected if the storage permissions have already been set. This container is just an init step to ensure correct permissions and will always stop after running; it does not indicate an error by itself. After this, the main application containers (like api, worker, etc.) should start automatically. If you see "no response" from the app, the issue is likely with those main containers or their dependencies (such as the database or redis), not with the init_permissions container itself.

To troubleshoot, check the status of all containers with docker compose ps or docker ps, and review the logs of the main services (api, worker, web, etc.) using docker compose logs to find any errors or reasons for failure to start. Also, check the health and logs of your database and redis containers, as issues there can block startup. If you find errors in those logs, sharing them will help with further diagnosis.

For more details, see the implementation and expected behavior in the docker-compose.yaml and related PR.

To reply, just mention @dosu.

---

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

   

[kurokobo]

As Dosu explained, it is normal behavior for the init_permissions container to become Exited.
This is one of the containers commonly known as "init containers" (feel free to look it up if you're interested).

This container is designed to set the storage permissions once before the api or worker containers start, and then exit immediately after completing the command.
Once the storage permissions are initialized at startup, there’s no need for ongoing changes, so there’s no reason for this container to keep running.