Jump to content
  • [6.12.8] Docker's "Update All" button uses outdated info, recreates containers I deleted

    • Solved Minor

    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:


    How to recreate:

    1. With 3 or more out of date Docker containers, load the Docker tab
    2. Don't reload the page or navigate away, this needs to be done in the same session
    3. Delete 1 container
    4. Update 1 container individually
    5. Click the 'Update All' button

    What I expect to happen:

    1. The deleted container stays deleted
    2. The manually-updated container is left alone, since it is already up to date
    3. The rest of the containers are updated to newest versions as usual

    What actually happens:

    1. The deleted container is recreated, but at the newest image version
    2. The container you already updated is deleted and recreated at the same version
    3. The other containers update as expected




    User Feedback

    Recommended Comments

    You are correct.  That page isn't considering that you would hit update all after removing a container without reloading the page.


    IE: Simple workaround is to reload the page before hitting update all if you've deleted something, but yes you found a bug

    • Upvote 1
    Link to comment

    This may partially explain the update loop that happens sometimes. I've always had a sense that when the loop happens it's using old information.

    Link to comment
    28 minutes ago, JonathanM said:

    update loop

    Hit check for updates multiple times without ever navigating away from the page.   Or do pretty much anything on the page without navigating away, and when you finally hit Update All, then you'll get an "update" issued for the same containers.  Number of times the "update" happens equals number of times you did something on that page.


    Kudos to @HastyBacon for figuring out the steps to replicate so the one-line fix can be implemented

    Link to comment

    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.

    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

  • Status Definitions


    Open = Under consideration.


    Solved = The issue has been resolved.


    Solved version = The issue has been resolved in the indicated release version.


    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.


    Retest = Please retest in latest release.

    Priority Definitions


    Minor = Something not working correctly.


    Urgent = Server crash, data loss, or other showstopper.


    Annoyance = Doesn't affect functionality but should be fixed.


    Other = Announcement or other non-issue.

  • Create New...