The CentOS, Fedora, and RHEL versions of Docker 1.10 have a patch that will allow you to push from Docker 1.10 to a schema2 enabled registry using schema1 (which is what we're using today in our CI). I believe it's --skip-schema2-push to the daemon and will be enabled soon in testing.
> On Jul 21, 2016, at 3:20 AM, Guilherme Macedo <[email protected]> wrote: > > Hi Clayton. > > Thanks for answering. > So I will wait for v1.3.0 release then, and will continue to push images > manually. > > Best regards. > > Guilherme Macedo | [email protected] > Information Security Consultant > www.gmacedo.com > > On Wed, 20 Jul 2016 19:06:48 -0400 > Clayton Coleman <[email protected]> wrote: > >> Accept schema2 is not supported in 1.2.0 >> >>> On Jul 20, 2016, at 6:33 PM, Guilherme Macedo <[email protected]> wrote: >>> >>> Hi. >>> >>> I'm running an Origin v1.2.0 cluster and docker v1.10.3-44 in our clients. >>> Origin fails to pull images from Docker Hub when I build a project with >>> Dockerfile due to manifest v2 schema change - manifest unknown error. >>> I've tried to set the variable >>> REGISTRY_MIDDLEWARE_REPOSITORY_OPENSHIFT_ACCEPTSCHEMA2 to true as >>> documented here [1], but Origin continues to fail with the same error. >>> To work around it I'm pulling images locally and pushing them to an Origin >>> registry that I exposed to our users. >>> Does anyone knows how to resolve this or we need to wait for Origin v1.3.0? >>> >>> [1] >>> https://docs.openshift.org/latest/install_config/install/docker_registry.html#docker-registry-configuration-reference-middleware >>> >>> Thanks in advance and best regards. >>> >>> Guilherme Macedo | [email protected] >>> Information Security Consultant >>> www.gmacedo.com >>> >>> _______________________________________________ >>> users mailing list >>> [email protected] >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
