origin: Origin 3.6 internal registry resolution failure
We have installed a Origin 3.6 instance on our development environment and we pushed some images into the internal registry with success. If we try to start a new deployment with this images the POD fails its pull action from the registry because it can’t resolve the address docker-registry.default.svc.
Failed to pull image "docker-registry.default.svc:5000/test-shared/haproxy@sha256:424a91dde92e2db9b8b9135bcb06e6b1c53645ee7c0ce274287c570e15f1a4b3": rpc error: code = 2 desc = Get https://docker-registry.default.svc:5000/v2/: dial tcp: lookup docker-registry.default.svc on 10.224.20.20:53: no such host
Version
oc v3.6.0+c4dd4cf
kubernetes v1.6.1+5115d708d7
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://dev-openshift.test.it:8443
openshift v3.6.0+c4dd4cf
kubernetes v1.6.1+5115d708d7
Steps To Reproduce
- from external servere oc login and docker push of the image on the internal registry
- from web-ui adding a new item to the project and run a new image with one replica
Current Result
The pod fails the creation with the error reported below.
Expected Result
The pod pulls the image from the registry.
Additional Information
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 44 (19 by maintainers)
In my case (OCP 3.9) I had to add this to ‘/etc/dnsmasq.d/node-dnsmasq.conf’ and restart dnsmasq.
Hey, sorry for the late reply.
We were able to get things working on 3.11 using this.
We had a couple issues which were causing different problems. There are still a few things we are working out as well. Thanks for the help.
Worked for me
I encountered a similar problem with 3.11. In testing:
dig +showsearch docker-registry.default.svc resolved to 92.242.140.21 dig +showsearch docker-registry.default.svc.cluster.local resolved to 172.30.89.2
As a less than ideal workaround, adding ‘172.30.89.2 docker-registry.default.svc’ to /etc/hosts and restarting the cluster (including docker) worked for me.
@markandrewj What’s in your /etc/resolv.conf on the host? It should have added cluster.local to the search path. What does
dig +showsearch docker-registry.default.svcshow you?This again happened:
https://ci.openshift.redhat.com/jenkins/job/test_branch_origin_extended_image_ecosystem/388/
Thanks for the followup, I’m going to say this was addressed by https://github.com/openshift/openshift-ansible/pull/5145 then