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.On Wed, Sep 28, 2016 at 5:08 PM, Gerard Braad <[email protected]> wrote: > On Wed, Sep 28, 2016 at 10:56 PM, Michail Kargakis <[email protected]> > wrote: > > 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? > > I just did a clean install of F24 on a new instance > > $ dnf update -y > $ dnf install -y curl docker git > $ vi /etc/sysconfig/docker # add --insecure-regsitry > $ systemctl start docker > $ curl -sSL https://github.com/openshift/origin/releases/download/v1.3. > 0/openshift-origin-client-tools-v1.3.0-3ab7af3d097b57f933eccef684a714 > f2368804e7-linux-64bit.tar.gz > -o oc-client.tar.gz > $ tar -zxvf oc-client.tar.gz > $ mkdir -p /opt/openshift/client > $ cp ./openshift-origin-client-tools-v1.3.0-3ab7af3d097b57f933eccef684a714 > f2368804e7-linux-64bit/oc > /opt/openshift/client/oc > $ export PATH=$PATH:/opt/openshift/client/ > $ oc cluster up > $ oc new-app openshift/ruby-20-centos7~https://github.com/openshift/ruby- > ex > > Same problem reported... >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
