Pain point · Self-hosting & upgrades · Causes churn
Update to 2024.4.2 invalidated docker-compose.yml and stack won't start
2 source threads · first seen 2024-05 · last seen 2025-08
Summary
After updating a long-running self-hosted instance, the generated compose file became invalid and the stack would not start; root cause appears to be an old docker-compose version despite docs saying it should work.
- Affects
- Self-hoster
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“The Nginx container keeps restarting and bitwarden cannot be accessed”
“my `docker-compose.yml` is now invalid, and bitwarden will no longer start”