Damn, I just went through having to downgrade my registry because I was pushing with 1.12 and openshift (running docker 1.10) wasn't able to pull the image due the the sha256 hash that it was referencing not existing because of the v1/v2 issues. I guess my only option if I don't want to upgrade my openshift is to push from a machine running docker 1.10?
On Thu, Aug 11, 2016 at 4:30 PM, Philippe Lafoucrière < philippe.lafoucri...@tech-angels.com> wrote: > If you are using different versions of docker on openshift, and the server > where the image was build, you will fall into this (known) problem. > Check out https://trello.com/c/CJiUnVUm/136-3-docker-1-10-push- > force-schema1-manifest-via-daemon-flag > > Hopefuly, this seems to be fixed in the upcoming 1.3. Check the section : > Upgrading to Docker Registry 2.4, cross-repository linking, and better > usage tooling > in https://github.com/openshift/origin/releases/tag/v1.3.0-alpha.3 > >
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
