Docker Container Updates Stuck on Loop

[N¿¿B]

Hello!

 

Ever since updating to 6.11.X, I've noticed that when I click "Update All", it will update all my containers and then after it reaches the last one, it will start back over and just continue to update from the top. This keeps repeating until I refresh the page. There is no longer any "Done" button once the updates have all taken place. The containers look like they updated, so it doesn't look like anything is really broken, but I'm not sure. Everything seems to be working fine. I thought by updating to 6.11.1 this would be fixed, but the issue is still there. Thanks for all your help!

[FalconX]

Can confirm - had this happened to me today. Clicked the "Update All" button, it updated the containers and got stuck in a loop where it would keep trying every single one again.

 

Refreshing didn't solve it either, as the logs still kept telling me containers were getting updated. Had to do a complete restart of the server.

 

I'm on Version: 6.11.1

[Liqwid_Kirk]

That is also happening to me. I'm also getting this message when I try to go to the container and update it individually

"Configuration not found. Was this container created using this plugin?"

Any help would be appreciated

[cave]

I've watched the same dockers behind a docker VPN restart for 40 minutes.  Still present in 6.11.5

Edited December 8, 2022 by cave

[bigbangus]

Just happened to me while I cherry picked some container updates that were pending for days. I finally had only 2 left to update and I hit update all and they just looped forever. Maybe this is a reproducible pattern to test with devs.

 

Had to restart server.

[sphbecker]

Just had the same exact problem on 6.12.3. Manually updated 1 container, then realized I had several more and just pressed Update All. Now stuck in an update loop.

 

EDIT: I pressed Stop All, which didn't end the update loop, but then pressed Check of Updates, which after completing the current cycle did seem to stop the loop. I was then able to start the dockers normally. Not a great solution, but it at least prevented a full server reboot.

Edited July 24, 2023 by sphbecker

[sphbecker]

Just had this issue happen again on 6.12.4, this time I couldn't do anything to stop the loop but reboot the system.

[ALERT]

Just happened to me on Version: 6.12.6.

[andrut]

Happened to me on 6.12.10