New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Following cluster up getting started documentation will lead to "did not detect an --insecure-registry argument on the Docker daemon" #21172

Open
tiraboschi opened this Issue Oct 4, 2018 · 3 comments

Comments

Projects
None yet
6 participants
@tiraboschi

tiraboschi commented Oct 4, 2018

Following cluster up getting started documentation will lead to "did not detect an --insecure-registry argument on the Docker daemon".

https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md#getting-started says that you have to set

[registries.insecure]
registries = ['172.30.0.0/16']

in /etc/containers/registries.conf OR

{
   "insecure-registries": [
     "172.30.0.0/16"
   ]
}

in /etc/docker/daemon.json but you instead need BOTH.

Then

$ sudo systemctl daemon-reload
$ sudo systemctl restart docker
Version
[stirabos@openshift linux]$ oc version
oc v3.11.0-alpha.0+f7602dd-1284
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO
[stirabos@openshift linux]$ yum list installed | grep docker
docker.x86_64                        2:1.13.1-75.git8633870.el7.centos @extras  
docker-client.x86_64                 2:1.13.1-75.git8633870.el7.centos @extras  
docker-common.x86_64                 2:1.13.1-75.git8633870.el7.centos @extras  
python-docker-pycreds.noarch         1.10.6-4.el7                      @extras  
python2-docker.noarch                2.4.2-1.el7.centos                @ansible-service-broker
Steps To Reproduce
  1. Try to deploy con Centos 7 following https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md#getting-started
  2. oc cluster up
Current Result
did not detect an --insecure-registry argument on the Docker daemon
Expected Result

Successful deployment

Additional Information

[try to run $ oc adm diagnostics (or oadm diagnostics) command if possible]
[if you are reporting issue related to builds, provide build logs with BUILD_LOGLEVEL=5]
[consider attaching output of the $ oc get all -o json -n <namespace> command to the issue]
[visit https://docs.openshift.org/latest/welcome/index.html]

@jwforres

This comment has been minimized.

Show comment
Hide comment
@jwforres
Member

jwforres commented Oct 11, 2018

@mtrmac

This comment has been minimized.

Show comment
Hide comment
@mtrmac

mtrmac Oct 11, 2018

Contributor

@tiraboschi Do you have the atomic-registries package installed and working?

The contents of /etc/containers/registries.conf should ordinarily be converted into a /run/containers/registries.conf which causes --insecure-registry options to be added among the options passed to the docker daemon.

Or maybe you need just an systemctl restart registries.service before restarting the Docker daemon?

Contributor

mtrmac commented Oct 11, 2018

@tiraboschi Do you have the atomic-registries package installed and working?

The contents of /etc/containers/registries.conf should ordinarily be converted into a /run/containers/registries.conf which causes --insecure-registry options to be added among the options passed to the docker daemon.

Or maybe you need just an systemctl restart registries.service before restarting the Docker daemon?

@vchepeli

This comment has been minimized.

Show comment
Hide comment
@vchepeli

vchepeli Oct 18, 2018

@tiraboschi without systemctl restart registries.service no file is created in /run/containers/registries.conf. Then when you run systemctl restart docker.service it automatically load registries from /run/containers/registries.conf

cat /run/containers/registries.conf
REGISTRIES="--add-registry registry.centos.org --add-registry registry.access.redhat.com --add-registry docker.io --insecure-registry 172.30.0.0/16"

vchepeli commented Oct 18, 2018

@tiraboschi without systemctl restart registries.service no file is created in /run/containers/registries.conf. Then when you run systemctl restart docker.service it automatically load registries from /run/containers/registries.conf

cat /run/containers/registries.conf
REGISTRIES="--add-registry registry.centos.org --add-registry registry.access.redhat.com --add-registry docker.io --insecure-registry 172.30.0.0/16"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment