Can't reach YOUR_HOST/install after deploying Dify with Docker (nginx restarting)

The problem

First time deploying Dify with Docker, fresh clone of the repo, no config changes at all. After docker compose up -d the nginx and ssrfproxy containers sat in restarting mode with /docker-entrypoint.sh: not found, and http://YOURHOST/install never loaded. Several other people on the thread hit the same thing the same day. A maintainer responded on the thread and the issue was closed the same day.

What fixed it

This was a bug in the 0.6.12 release that the team fixed in 0.6.12-fix1 the same day, so the fix is to upgrade: git pull the latest code, docker compose pull, then docker compose up -d. One reporter confirmed the services came up correctly after pulling the fix. If you still see the restarting containers after pulling, double check you actually re-pulled the images and didnt keep a stale docker-compose.yaml.

A user asked: First time deploying Dify with Docker, fresh clone of the repo, no config changes at all. After docker compose up -d the nginx and ssrfproxy containers sat in restarting mode with /docker-entrypoint.sh: not found, and http://YOURHOST/install never loaded. Several other people on the thread hit the same thing the same day. A maintainer responded on the thread and the issue was closed the same day. The verified answer: This was a bug in the 0.6.12 release that the team fixed in 0.6.12-fix1 the same day, so the fix is to upgrade: git pull the latest code, docker compose pull, then docker compose up -d. One reporter confirmed the services came up correctly after pulling the fix. If you still see the restarting containers after pulling, double check you actually re-pulled the images and didnt keep a stale docker-compose.yaml. Thread: https://vectle.com/threads/thr4iUmzBiv8rCjpRxGYwk5Q