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


    urbanracer34
    • 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



    Are you using pihole as DNS server for your Unraid machine?

     

    When network connection issues exist, it may result in the behavior you are seeing.

     

    Share this comment


    Link to comment
    Share on other sites

    This issue is effecting a wide swath of people. Personally I have 27 containers on one of my servers, all 10 of the LSIO show update ready, none of the other containers do. They were all up to date yesterday.

     

    No connection issues at my end of the pipe, one of my other servers behind the same router just updated a binhex container just fine.

     

    A different server at another location with 10 containers, all 3 of the LSIO show update ready. If it's unraid's fault, then unraid is preferentially picking on LSIO.

    Share this comment


    Link to comment
    Share on other sites
    50 minutes ago, bonienl said:

    Are you using pihole as DNS server for your Unraid machine?

     

    When network connection issues exist, it may result in the behavior you are seeing.

     

    No. No pihole here.

    10 minutes ago, jonathanm said:

    This issue is effecting a wide swath of people. Personally I have 27 containers on one of my servers, all 10 of the LSIO show update ready, none of the other containers do. They were all up to date yesterday.

     

    No connection issues at my end of the pipe, one of my other servers behind the same router just updated a binhex container just fine.

     

    A different server at another location with 10 containers, all 3 of the LSIO show update ready. If it's unraid's fault, then unraid is preferentially picking on LSIO.

    I am not having any connection issues here AFAIK. Connection has been stable.

    Share this comment


    Link to comment
    Share on other sites
    16 minutes ago, jonathanm said:

    If it's unraid's fault, then unraid is preferentially picking on LSIO.

    Ah, maybe I need to change this part of the code 😉

    if (container_author == "LSIO")
    then return_message "update ready"
    else check_for_update()

     

    Share this comment


    Link to comment
    Share on other sites

    I have 14 containers - 8 containers show update ready. Update all, check for update and again show update ready.

    Share this comment


    Link to comment
    Share on other sites

    I am too having issues updating my LSIO dockers.  Same thing showing update and its pulls nothing.

    Share this comment


    Link to comment
    Share on other sites

    Same thing here...  have several containers showing updates but there really isn't.  Seems to be containers that had updates in the past few days or so.  

    Share this comment


    Link to comment
    Share on other sites

    Also having this issue, only with linuxserver repositories.

    Share this comment


    Link to comment
    Share on other sites

    Same for me, all the LSIO containers show updates without pulling any data by starting the process.

    Share this comment


    Link to comment
    Share on other sites

    If it's not an unraid issue, the issue is docker hub.

    We don't have any more failed builds than normal at our end and if we would have gotten any problems pushing to docker hub our build pipeline would have made an error.

    Share this comment


    Link to comment
    Share on other sites

    FWIW, I checked our containers that I run on my own server, when updating them one by one the update notification went away.

     

    I was discussing this with @urbanracer34 last night and it seems it could be an error with the "update all containers button".

    Share this comment


    Link to comment
    Share on other sites
    bastl

    Posted (edited)

    2 minutes ago, j0nnymoe said:

    FWIW, I checked our containers that I run on my own server, when updating them one by one the update notification went away.

     

    I was discussing this with @urbanracer34 last night and it seems it could be an error with the "update all containers button".

    After updating each one by one, search for updates again and all your dockers will show updates as before. If you look at the output of the update window, you will see it pulls 0 data.

    Edited by bastl

    Share this comment


    Link to comment
    Share on other sites
    17 minutes ago, bastl said:

    After updating each one by one, search for updates again and all your dockers will show updates as before. If you look at the output of the update window, you will see it pulls 0 data.

    The only thing I can think of is something has changed at docker hub which is causing unraid's update checker to think there is an update. We've not changed our release workflow since we implemented pipeline (6 months ago).

    Share this comment


    Link to comment
    Share on other sites

    Updating the one by one does not help on my end. Also if I update just 1 of the LSIO containers it will show that it has an update available immediately after updating and checking for updates.

     

    Share this comment


    Link to comment
    Share on other sites

    I just tried creating a new docker.img file, which is a common fix for this kind of problem, and it still gets the same problem when I start re-adding my LSIO Docker containers.

     

    Interestingly I've have the same problem with the oauth2proxy container hosted from quay.io. Unraid always thinks there's an update for it even though there is none. I have a feeling these two problems might be connected somehow.

    Share this comment


    Link to comment
    Share on other sites

    I've seen a comment from someone on our discord that it could be an AWS issue.

    Share this comment


    Link to comment
    Share on other sites
    Squid

    Posted (edited)

    1 hour ago, j0nnymoe said:

    I've seen a comment from someone on our discord that it could be an AWS issue.

    Interestingly enough, only my containers from LSIO are suffering from that.  Everything else (binhex, djoss, etc) does not show an update unless one actually is available.

     

    To my workflow however it's irrelevant as I use the auto update plugin to just handle everything for me daily, and never ever go to the docker page and check for updates.

    Edited by Squid

    Share this comment


    Link to comment
    Share on other sites

    I don't know how others build their container, but we build all in Jenkins (might be an exception or two) and I'm not sure if everyone else is doing that. So that might be the difference. Might be something happened with the api regarding pushed images.

     

    However, I don't see that this is something we could fix as we do not host any images ourself and everything is on docker hub, so any issues with checking for updates is not under our control. It's either docker that have an issue or unraids update check (change in api in newer versions?)

     

     

    Share this comment


    Link to comment
    Share on other sites

    My suspicion is something changed at docker hub and there is a mismatch with the Unraid implementation.

     

    Needs to be investigated though and strange (if true) it only affects LSIO containers.

     

    Share this comment


    Link to comment
    Share on other sites

    I'm also seeing this with the pihole/pihole container I installed last night after switching from diginc/pihole

    Share this comment


    Link to comment
    Share on other sites

    I just noticed it has affected my Home Assistant Docker as well.  So its just not LSIO dockers only.

    Share this comment


    Link to comment
    Share on other sites

    Anyone know if it was caused by the Community Applications plugin update on 8/27?

    Edited by rsuplido

    Share this comment


    Link to comment
    Share on other sites
    14 minutes ago, rsuplido said:

    Anyone know if it was caused by the Community Applications plugin update on 8/27?

    No. I had this issue before updating CA today.

    Share this comment


    Link to comment
    Share on other sites

    Not LSIO dockers only:

    pihole/pihole
    raymondmm/tasmoadmin
    linuxserver/letsencrypt
    linuxserver/oscam
    library/influxdb
    linuxserver/duckdns
    homeassistant/home-assistant
    library/telegraf
    linuxserver/sonarr
    linuxserver/transmission
     

    Share this comment


    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.