hurricanehrndz Posted May 8, 2015 Share Posted May 8, 2015 Hey I'm just noticing sometimes the plugin doesn't come back with an update available when there is one. Link to comment
sparklyballs Posted May 8, 2015 Share Posted May 8, 2015 docker hub is doing some weird stuff the last two weeks or so, so it's hard to tell if it's them or the plugin. Link to comment
aptalca Posted May 8, 2015 Share Posted May 8, 2015 I noticed that today, too. I had to force updates in the Advanced View Link to comment
sparklyballs Posted May 11, 2015 Share Posted May 11, 2015 it's getting worse, dockerhub is almost always plagued issues , at least for the last month or so. anyways, now if you run a build there's a new thing i'm noticing, the new build on the summary screen where it says 3 hours ago etc... that time on there is before i even finished writing the container, i had one earlier i finished the container, pushed it to git and started a new autobuild on dockerhub and it took about 20 minutes to build and the time said 18 hours ago. Link to comment
NAS Posted May 11, 2015 Share Posted May 11, 2015 Perhaps a better way would be to maintain some location with a list of containers that are ready to use. This would allow developers better control of when to make something available and not rely or race with the publishing process to dockerhub. It alos opens the door for deprecating versions, changelog inclusion and perhaps even dependency's. Link to comment
sparklyballs Posted May 11, 2015 Share Posted May 11, 2015 it is now completely unusable regards updated containers. my build box container get's updated all the time as i try new builds. dockerhub is telling me in the top corner it was last updated 4 days ago, the build history say's otherwise. it's pulling the build from 4 days ago in dockerman. Link to comment
BRiT Posted May 11, 2015 Share Posted May 11, 2015 Perhaps a better way would be to maintain some location with a list of containers that are ready to use. This would allow developers better control of when to make something available and not rely or race with the publishing process to dockerhub. It alos opens the door for deprecating versions, changelog inclusion and perhaps even dependency's. It also closes the door on using the wide variety of existing Dockers. One should not reinvent the wheel especially when you're not the one controlling the standard and are more in need of what others provide than they are inneed of what you provide. Dockerhub is that standard. They just need to gettheir growth issues under control. No need to kill the child just because they're going through a phase and in their terrible twos. Things will get better. Link to comment
gfjardim Posted May 11, 2015 Share Posted May 11, 2015 I think you just stumble upon a Docker Hub bug: https://index.docker.io/v1/repositories/sparklyballs/isengard-builder-box/images https://index.docker.io/v1/repositories/sparklyballs/isengard-builder-box/tags/latest Both should return JSON formatted data, but just one is. Link to comment
NAS Posted May 12, 2015 Share Posted May 12, 2015 Perhaps a better way would be to maintain some location with a list of containers that are ready to use. This would allow developers better control of when to make something available and not rely or race with the publishing process to dockerhub. It alos opens the door for deprecating versions, changelog inclusion and perhaps even dependency's. It also closes the door on using the wide variety of existing Dockers. One should not reinvent the wheel especially when you're not the one controlling the standard and are more in need of what others provide than they are inneed of what you provide. Dockerhub is that standard. They just need to get their growth issues under control. No need to kill the child just because they're going through a phase and in their terrible twos. Things will get better. I agree but I am also thinking about the necessary move towards group working and a peer review group which obviously needs many things including pre go live staging. How would we achieve this using the current mechanism? Link to comment
Squid Posted May 12, 2015 Share Posted May 12, 2015 http://en.m.wikipedia.org/wiki/Quis_custodiet_ipsos_custodes%3F Link to comment
sparklyballs Posted May 12, 2015 Share Posted May 12, 2015 http://en.m.wikipedia.org/wiki/Quis_custodiet_ipsos_custodes%3F just call me dr manhattan Link to comment
exist2resist Posted May 13, 2015 Share Posted May 13, 2015 Yeah I'm also having issues with docker, it's not able to check for newer container versions. Link to comment
sparklyballs Posted May 14, 2015 Share Posted May 14, 2015 I noticed that today, too. I had to force updates in the Advanced View that's not even working any more. i've triggered 4 rebuilds on a new container i created with really big changes on each version (deliberately, to test updates etc) and dockerman is pulling the first build every single time. dockerhub as it stands right now is utterly unusable if you have to update any containers........... Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.