Parallel container image updates #227

New issue

Open

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

deekerman commented

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

Owner

Originally created by @truthsword on GitHub (Oct 1, 2025).

⚠️ 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

Ran through a series of container updates (click, click, click...)

But in the end many containers were trashed, and when called, defaulted to their OOB set-up screens (OMG, npt Plex and Portainer).

👟 Reproduction steps

Select multiple container updates without waiting between containers to finish their update.

👀 Expected behavior

Expected updated container to work where they left off.

😓 Actual Behavior

Many containers opened to their welcome screens asking to set up new users!

Dockge Version

1.5

💻 Operating System and Arch

Debian 12

🌐 Browser

Firefox, Edge...

🐋 Docker Version

28.3.3

🟩 NodeJS Version

No response

📝 Relevant log output

Nothing unusual from docker... but in updated container logs many failures.

Oddly... I was able to regain access to containers simply by 
`docker compose down && docker compose up -d`

Is it wrong to initiate multiple container updates with Dockge? I haven't seen this happen before.

Originally created by @truthsword on GitHub (Oct 1, 2025). ### ⚠️ 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 Ran through a series of container updates (click, click, click...) But in the end many containers were trashed, and when called, defaulted to their OOB set-up screens (OMG, npt Plex and Portainer). ### 👟 Reproduction steps Select multiple container updates without waiting between containers to finish their update. ### 👀 Expected behavior Expected updated container to work where they left off. ### 😓 Actual Behavior Many containers opened to their welcome screens asking to set up new users! ### Dockge Version 1.5 ### 💻 Operating System and Arch Debian 12 ### 🌐 Browser Firefox, Edge... ### 🐋 Docker Version 28.3.3 ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output ```shell Nothing unusual from docker... but in updated container logs many failures. Oddly... I was able to regain access to containers simply by `docker compose down && docker compose up -d` Is it wrong to initiate multiple container updates with Dockge? I haven't seen this happen before. ```