Hey Gerard, I also hit this issue this morning: https://paste.fedoraproject.org/438222/51651371/
Seems that a recent change to docker (projectatomic/docker) introduced a regression: $ git describe v1.10.3-95-g8b7fa4a $ git log --oneline a612434.. | grep -i digest 8e24cc3 Merge pull request #194 from runcom/backport-pulldigests-fedora 6c0bb14 Do not show empty tags for digest references in output a216b04 Treat digest only images as dangling 34771e8 Always store the image digest when pulling and pushing an image. I'm thinking 34771e8, though I've yet to prove it. You can go to koji and downgrade to an old version (this is the one I used): http://koji.fedoraproject.org/koji/buildinfo?buildID=796377 I've opened a bug to track this: https://bugzilla.redhat.com/show_bug.cgi?id=1380474 Thanks, Seth On Thu, Sep 29, 2016 at 11:47 AM, Andy Goldstein <[email protected]> wrote: > cc Seth, who has done some more investigation and will reply with an update. > > Andy > > On Wed, Sep 28, 2016 at 11:30 AM, Gerard Braad <[email protected]> wrote: >> >> On Wed, Sep 28, 2016 at 11:22 PM, Michail Kargakis <[email protected]> >> wrote: >> > You can work around this by pulling by tag instead of by hash. Try >> > setting >> > {DOCKER-REGISTRY-IP}/myproject/ruby-ex:latest instead of >> > {DOCKER-REGISTRY-IP}/myproject/ruby-ex@sha256:... in your DC. >> > Not sure how pull by hash can be fixed though. >> >> Unfortunately, the image is not available as mentioned before: >> >> # docker pull 172.30.151.66:5000/myproject/ruby-ex:latest >> Trying to pull repository 172.30.151.66:5000/myproject/ruby-ex ... >> Pulling repository 172.30.151.66:5000/myproject/ruby-ex >> Error: image myproject/ruby-ex not found > > _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
