Diagnosis (no repair attempted). coatrack is crash-looping (exit 1, 14+ restarts, not OOM). postgres is healthy and reachable: the entrypoint gets to "PostgreSQL is ready". The failure is in /app/migrate.py: create_engine() loads SQLAlchemy's postgresql+psycopg (psycopg v3) dialect, and import psycopg raises ModuleNotFoundError. So the locally built image dragonhive-coatrack-coatrack has a dependency mismatch: the code or config wants psycopg3, but the image doesn't install it (it may only ship psycopg2, or nothing). This most likely comes from upstream commit 660060ce -> 25369277. The rollback did not help. The current container was created at 03:45:37, after the rollback, and still fails the same way. My guess is the rollback reused the same locally tagged image, or didn't rebuild from the old commit, so the broken build is still running. A human should check this. Why I didn't act: a restart or up would rerun the same image and hit the same ImportError. Running pip install inside the container isn't a service-native fix, wouldn't survive a restart, and no exec scope is configured anyway. Suggested fix: either rebuild from the previous commit 660060ce (git checkout 660060ce && docker compose build --no-cache coatrack && docker compose up -d), or fix requirements upstream by adding psycopg[binary] or switching the URL/driver back to psycopg2. The database was not touched. Side finding: migrate.py prints the full DATABASE_URL, password included, to the container logs. That's worth fixing upstream, and if the logs have been shipped anywhere, consider rotating the password.