It looks like the "Update All" button caches the Docker state at page load and uses that cache to determine which containers need to be updated. It should actually be fetching the current configuration at the moment you press the button.
This results in:
- Containers being "updated" when they're already up to date, causing service interruption
- Deleted containers being recreated
How to recreate:
- With 3 or more out of date Docker containers, load the Docker tab
- Don't reload the page or navigate away, this needs to be done in the same session
- Delete 1 container
- Update 1 container individually
- Click the 'Update All' button
What I expect to happen:
- The deleted container stays deleted
- The manually-updated container is left alone, since it is already up to date
- The rest of the containers are updated to newest versions as usual
What actually happens:
- The deleted container is recreated, but at the newest image version
- The container you already updated is deleted and recreated at the same version
- The other containers update as expected
Recommended Comments
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.