Red Hat Bugzilla – Bug 1460930
docker is using a new configure file to defined registries
Last modified: 2017-09-18 14:39:41 EDT
Description of problem:
docker-1.12.6-34 is using "/etc/containers/registries.conf" instead of "/etc/sysconfig/docker" to defined registries. But installer is still add registries to "/etc/sysconfig/docker".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Install OCP with docker-1.12.6-34
# cat /etc/sysconfig/docker
# Do not add registries in this file anymore. Use /etc/containers/registries.conf
# from the atomic-registries package.
ADD_REGISTRY='--add-registry ... --add-registry registry.access.redhat.com'
According to document in "/etc/sysconfig/docker", installer should add registries in "/etc/containers/registries.conf".
Is this a mandatory change or will the old environment files work?
(In reply to Scott Dodson from comment #1)
> Is this a mandatory change or will the old environment files work?
According to my testing, the old environment file still works.
Mine too, moved to 3.7.
PR created in github: https://github.com/openshift/openshift-ansible/pull/5205
The original configuration file /etc/sysconfig/docker is still honored and there has been no discussion about EOL'ing it. The only difference is that registries in the sysconfig/docker file will not be usably by other container runtimes or skopeo.
There are some discussions on that PR regarding which container runtimes are currently consuming /etc/containers/registries.conf
Having one registry configuration file for all runtimes would be beneficial to openshift-ansible users and allow our codebase to simplify.