[CentOS-devel] Docker daemon not respecting the insecure registry which is part of /etc/containers/registry.conf
Praveen Kumar
kumarpraveen.nitdgp at gmail.comThu Jun 14 10:55:55 UTC 2018
- Previous message: [CentOS-devel] Latest podman installation broken in CentOS
- Next message: [CentOS-devel] Removing old centos-release-<sig-project><version> from CentOS Extras?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, I spun up a fresh centos-7.5 VM on Digital ocean and tried to do oc cluster up which require to have insecure registry `172.30.0.0/16` when I am trying to add this in the /etc/containers/registry.conf this is not picked up by docker daemon even after restart:( I can see we have `/run/containers/registries.conf` as env file in the `/usr/lib/systemd/system/docker.service` which even not present on the system :( Not sure where we messed up or I made some mistake here. ``` # rpm -qa | grep docker docker-common-1.13.1-63.git94f4240.el7.centos.x86_64 docker-1.13.1-63.git94f4240.el7.centos.x86_64 docker-client-1.13.1-63.git94f4240.el7.centos.x86_64 ``` Note: Same addition of insecure registry working as expected in the fedora28. -- Praveen Kumar http://fedoraproject.org/wiki/User:Kumarpraveen http://fedoraproject.org/ http://kumar-pravin.blogspot.com
- Previous message: [CentOS-devel] Latest podman installation broken in CentOS
- Next message: [CentOS-devel] Removing old centos-release-<sig-project><version> from CentOS Extras?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS-devel mailing list