June 21, 201610 yr May I casually redirect your attention to the following issue: At some point (an unclean shutdown?) docker starts reporting "updates ready" for all new/updated docker containers. On updating the container 0kb is downloaded and the bug persists. See here: http://lime-technology.com/forum/index.php?topic=49354.0
June 27, 201610 yr unRAID OS Version: 6.1.9 and 6.2 beta 23 (possibly other earlier betas too) Description: Docker image updates are not flagged in the unRAID Docker UI or are getting "stuck" with a UI status of "Updates available" when there are no updates to the Docker image. How to reproduce: Download a Docker image, get the owner of the Docker repo to push a change and noticed that "Updates available" do NOT show. Expected results: When updates are available for a Docker image then the "Updates available" button should highlight. Actual results: When updates are available the "Updates available" button does NOT highlight. Other information: As detailed above, this is also linked to the issue where the "Updates available" button gets stuck highlighted even when there are no changes to the Docker image to download (this looks more prevalent in 6.2 beta's) My gut feeling on why this is occurring is that there has been a change in the API for Docker hub and this has not been reflected in dockerman for unRAID and thus users are seeing a disconnect from the actual state of the image, users are able to pull images ok but dockerman cannot see the current docker id for the image on Docker Hub and therefore cannot do a compare of the id. Linking to this defect as its showing the disconnect from Docker Hub:- http://lime-technology.com/forum/index.php?topic=49897.0 Link to users complaining of this issue:- https://lime-technology.com/forum/index.php?topic=45845.msg476872#msg476872 http://lime-technology.com/forum/index.php?topic=49354.msg473513#msg473513 http://lime-technology.com/forum/index.php?topic=48251.msg462770#msg462770
July 8, 20169 yr I'm marking this as solved, by -rc1. I understand there are 3 forms of the docker update issue, but in general the problem appears to be fixed by the rc. If anyone knows differently, please speak up.
July 9, 20169 yr I'm marking this as solved, by -rc1. I understand there are 3 forms of the docker update issue, but in general the problem appears to be fixed by the rc. If anyone knows differently, please speak up. I think the Israel bug is still present, but it affected two users both in Israel/Middle East and Eric couldn't reproduce it, so I'd be surprised if that's fixed. The other one was a manifest error which I believe is fixed but may require a docker.img rebuild. The third was a 0 byte perpetual update, which has been fixed in RC1 for me. Think it was a http 400 error.
July 9, 20169 yr There is of course the issue with 6.1.9 in that you never get notification of updates for docker images (defect raised) but I got a horrible feeling this won't ever get fixed Sent from my SM-G900F using Tapatalk
Archived
This topic is now archived and is closed to further replies.