• Dockers wanting to update, but don't in the end?


    urbanracer34
    • Closed Minor

    So I appear to be having a problem with dockers, Specifically Linuxserver ones, but they said to me it is an unRAID issue and it is "not just us." I chatted with someone from Linuxserver in private and they said it is an issue with "Update all containers."

     

    The dockers will say there is an update ready, but when updated, it does not do anything.

     

    Tried manually updating a docker, same result. 

    gibson-diagnostics-20190829-1841.zip

    • Like 1


    User Feedback

    Recommended Comments



    5 minutes ago, mi5key said:

    Running 6.8.0 since released, this problem just popped up for me today.  All Docker containers say "update ready", updating manually does nothing.  Pulls 0 bytes, just reloads the container.

     

    So, not fixed in 6.8.

     

    I'm just now going through this whole thread.

    Probably a network glitch or some other transient event.  With 6.8.0, if unRaid can't communicate with dockerHub, it does show update available.  Try again later

    Link to comment
    Share on other sites
    22 minutes ago, Squid said:

    Probably a network glitch or some other transient event.  With 6.8.0, if unRaid can't communicate with dockerHub, it does show update available.  Try again later

    I added a second network cable yesterday, assigned an IP address, unraid made it the default route and that's when the problems started.  Both NICs have outbound access to the gateway/dns, but when unraid made the second NIC the default, that's when the problems started.

     

    I disabled the second NIC, manually added a default route via the first NIC, re-enabled the second NIC and now everything is working as normal.

     

    Likely not a bug in unraid, just changing the default route to the newest added NIC appears to be the issue.

    Link to comment
    Share on other sites
    5 minutes ago, mi5key said:

    Likely not a bug in unraid, just changing the default route to the newest added NIC appears to be the issue.

    @bonienl can help with the routing configuration

     

    The update always available though if unRaid can't reach dockerHub has been rectified under 6.8.1-rc1

    Link to comment
    Share on other sites
    1 minute ago, sduensin said:

    Closed?  I'm still seeing this in 6.8.3.

    Closed because this defect is fixed.  If you are having the same / similar problem, open a new thread within General Support.  Include your diagnostics, and screen shots showing the 0 byte pull

    Link to comment
    Share on other sites



    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.

    Guest
    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.