I just updated from docker 1.9 to docker 1.10 and can reproduce this issue. I managed to deploy by using the RepoTags instead of the RepoDigest. Is this a known issue in the sense that there is a fix to it or we can only pull by tags?
On Wed, Sep 28, 2016 at 4:26 PM, Andy Goldstein <agold...@redhat.com> wrote: > Can you run this command: > > sudo cat /var/lib/docker/image/devicemapper/repositories.json | python > -mjson.tool > > and find the repository entry for 172.30.165.95:5000/myproject/ruby-ex. > Then find the entry for http://172.30.165.95:5000/ > myproject/ruby-ex@sha256:df71f696941a9daa5daaea808cfcaa > f72071d7ad206833c1b95a5060dd95ca92 and see what sha256 it points to. Then > I would 'docker inspect' that value and see what it is. > > We had a bug in the past where when you had images pulled using our docker > 1.8 and then you upgraded to 1.9+, you would get this error. I'm not sure > why you'd see it on a clean 1.10.3 install, though :-( > > Andy > > On Wed, Sep 28, 2016 at 10:15 AM, Gerard Braad <m...@gbraad.nl> wrote: > >> On Wed, Sep 28, 2016 at 6:50 PM, Andy Goldstein <agold...@redhat.com> >> wrote: >> > Gerard, were you on docker 1.8 and did you then upgrade to 1.9 or 1.10? >> I >> > recall a bug we had that sounds similar to what you're seeing here. >> >> I had not done an upgrade at all. >> a clean cloud image install: >> >> $ dnf install -y curl docker >> $ docker -v >> Docker version 1.10.3, build 8b7fa4a/1.10.3 >> > >
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
