Recreation of container with new docker compose version #245

New issue

Open

opened 2026-02-20 13:12:32 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-20 13:12:32 -05:00

Owner

Originally created by @andreibrebene on GitHub (Feb 17, 2026).

⚠️ Please verify that this bug has NOT been reported before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

Description

When using Dockge to update a stack that includes the Dockge container itself, Docker Compose v5 aggressively recreates containers. This can stop or remove Dockge mid-update, causing the UI to become unresponsive and the stack to fail to fully start. It worked on Compose v2 because older versions were more forgiving with container recreation and ordering.

👟 Reproduction steps

Run stack update on dockge with docker compose version 5.0,2

👀 Expected behavior

Container administrated from dockge will recreate with another name and not mentain the defined container_name from docker-compose file.

😓 Actual Behavior

Should keep the container_name defined on docker compose file.

Dockge Version

1.5.0

💻 Operating System and Arch

Debian

🌐 Browser

Google Chrome

🐋 Docker Version

29.2.1

🟩 NodeJS Version

No response

📝 Relevant log output

Originally created by @andreibrebene on GitHub (Feb 17, 2026). ### ⚠️ Please verify that this bug has NOT been reported before. - [x] I checked and didn't find similar issue ### 🛡️ Security Policy - [x] I agree to have read this project [Security Policy](https://github.com/louislam/dockge/security/policy) ### Description When using Dockge to update a stack that includes the Dockge container itself, Docker Compose v5 aggressively recreates containers. This can stop or remove Dockge mid-update, causing the UI to become unresponsive and the stack to fail to fully start. It worked on Compose v2 because older versions were more forgiving with container recreation and ordering. ### 👟 Reproduction steps Run stack update on dockge with docker compose version 5.0,2 ### 👀 Expected behavior Container administrated from dockge will recreate with another name and not mentain the defined container_name from docker-compose file. ### 😓 Actual Behavior Should keep the container_name defined on docker compose file. ### Dockge Version 1.5.0 ### 💻 Operating System and Arch Debian ### 🌐 Browser Google Chrome ### 🐋 Docker Version 29.2.1 ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output ```shell ```