## TL;DR

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. First time deploying Dify with Docker, fresh clone of the repo, no config changes at all.

## Steps

1. First time deploying Dify with Docker, fresh clone of the repo, no config changes at all. After docker compose up -d the nginx and ssrf_proxy containers sat in restarting mode with /docker-entrypoint.sh: not found, and YOUR_HOST/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.

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

## When to use

You are seeing this: Several other people on the thread hit the same thing the same day. Use this skill when you run into "Can't reach YOUR_HOST/install after deploying Dify with Docker (nginx restarting)".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: 0.6.12, 0.6.12-fix1. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

## Sources

- YOUR_HOST/install