sparklyballs Posted January 22, 2015 Share Posted January 22, 2015 I'm really hoping this is just me making a school boy error but i've ran three new test builds this evening and i've noticed something strange over on docker hub. whenever i normally add a new automated build from github it gets tagged as latest, they're now getting tagged as master, and the template on unraid webui won't load them. and when i update an existing automated build, the new build is getting tagged as master and instead of just one tag of latest in the tags list on docker hub i'm getting both master and latest, when i pull builds tagged like this through the template here, i'm getting both the latest and the master pulled from docker hub, but only the older build will run. EDIT: - it is fixed now Quote Link to comment
sparklyballs Posted January 22, 2015 Author Share Posted January 22, 2015 Something is very wrong with docker hub at the moment. settings for an existing docker that has been updated several times tag section for it. settings for existing docker that was updated last night tag section for it. now when i try and update it from the template it pulls the master image, downloads like normal then fails at the removal stage saying image is being used by that container itself, and i get two images in the image list in docker webui, one saying <dockername>:latest and the other :master the :latest is greyed out for being in use and the master is selectable for deletion, delete it and reload info and the docker no longer shows blue. so basically as it stands, i can't make new containers or upload existing ones. i hope this is a temporary thing and/or is only affecting me, but i feel container authors should be aware and perhaps someone can test making a new container and see if it is also getting tagged master instead of latest or update an existing container (perhaps from a private or testing repo) Quote Link to comment
sparklyballs Posted January 22, 2015 Author Share Posted January 22, 2015 https://github.com/docker/docker/issues/10271 This is a real issue at present. Quote Link to comment
smdion Posted January 22, 2015 Share Posted January 22, 2015 https://github.com/docker/docker/issues/10271 This is a real issue at present. I won't be updating my dockers anytime soon. haha Quote Link to comment
sparklyballs Posted January 22, 2015 Author Share Posted January 22, 2015 https://github.com/docker/docker/issues/10271 This is a real issue at present. I won't be updating my dockers anytime soon. haha I pm'ed jonp about it. Quote Link to comment
sparklyballs Posted January 22, 2015 Author Share Posted January 22, 2015 i thought people should really know, i predict a lot of people updating their dockers soon because phusion baseimage just upped to 0.9.16 a couple of days ago. Quote Link to comment
jonp Posted January 22, 2015 Share Posted January 22, 2015 i thought people should really know, i predict a lot of people updating their dockers soon because phusion baseimage just upped to 0.9.16 a couple of days ago. Hopefully this will be a very quick fix from the Docker team. They are definitely aware and working on it from what I just read. Quote Link to comment
binhex Posted January 22, 2015 Share Posted January 22, 2015 Looks like it's just been fixed http://status.docker.com/pages/incident/533c6539221ae15e3f000031/54c135bce0354e3856000229 Quote Link to comment
sparklyballs Posted January 22, 2015 Author Share Posted January 22, 2015 Looks like it's just been fixed http://status.docker.com/pages/incident/533c6539221ae15e3f000031/54c135bce0354e3856000229 i'd say 1/2 fixed. whilst new builds are getting tagged correctly now, update builds are still getting tagged as master. Quote Link to comment
sparklyballs Posted January 22, 2015 Author Share Posted January 22, 2015 pulling this from docker hub via template results in this. note two instances of couchpotato2 :latest and :master :master is the newer build but the template is running the :latest. Quote Link to comment
binhex Posted January 22, 2015 Share Posted January 22, 2015 It looks OK for me, just forced a build on an existing docker and the tag is correct and pulls down correct too. Quote Link to comment
sparklyballs Posted January 22, 2015 Author Share Posted January 22, 2015 It looks OK for me, just forced a build on an existing docker and the tag is correct and pulls down correct too. i've tried two new and two update builds, new builds are fine, update builds result in the mess above. Quote Link to comment
binhex Posted January 22, 2015 Share Posted January 22, 2015 Have you clicking on "edit build details" and made sure the tag name is latest? It might be that the bug is fixed but is left your docker tags incorrectly defined as master. Quote Link to comment
sparklyballs Posted January 22, 2015 Author Share Posted January 22, 2015 Have you clicking on "edit build details" and made sure the tag name is latest? It might be that the bug is fixed but is left your docker tags incorrectly defined as master. just ran an update of a new build and it's still doing it. Quote Link to comment
binhex Posted January 22, 2015 Share Posted January 22, 2015 Updates are fine for me, tagged as latest, haven't tried a new build Quote Link to comment
saarg Posted January 23, 2015 Share Posted January 23, 2015 Have you clicking on "edit build details" and made sure the tag name is latest? It might be that the bug is fixed but is left your docker tags incorrectly defined as master. just ran an update of a new build and it's still doing it. I tried earlier to use the tag for different versions of my builds but ended up deleting the whole docker as it did the same thing as happens to you. It would download both tags no matter what and it's impossible to delete a tag after it's built. Might be ther is a way to do it, but I didn't figure out how. Quote Link to comment
Recommended Posts
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.