I tested the DNS on another docker and it seems work [root@dev-openshift01 ~]# oc get pods NAME READY STATUS RESTARTS AGE jenkins-1-1rzjg 1/1 Running 0 6h mariadb-1-ngjvt 1/1 Running 0 3m [root@dev-openshift01 ~]# oc rsh mariadb-1-ngjvt sh-4.2$ nslookup docker-registry.default.svc Server: 192.168.98.146 Address: 192.168.98.146#53
Name: docker-registry.default.svc.cluster.local Address: 172.30.179.158 The address reported from master node for the DNS server and the DNS server used into the docker image is different. Marcello On Fri, Aug 25, 2017 at 3:56 PM, Clayton Coleman <[email protected]> wrote: > This is likely a dns issue. Verify inside of a test pod that you have > access to docker-registry.default.svc via DNS (dig or nslookup) > > On Aug 25, 2017, at 3:59 AM, Marcello Lorenzi <[email protected]> wrote: > > Hi All, > we have installed the new Origin 3.6.0 version on our development > environment and we tried to push and pull some images generated outside > Origin installation but pushed with these commands to the internal registry: > > - oc login --username=test > - docker login -u test -e unused -p `oc whoaim > -t ` docker-registry-default.devapps.test.local > - oc logout > > The images are correctly visible on the docker registry console but if we > try to pull a new image from a pod we received some errors like: > > = Get https://docker-registry.default.svc:5000/v2/: dial tcp: lookup > docker-registry.default.svc on 10.224.21.21:53: no such host > > We have tried to exclude the IP from the docker proxy exclusion without > success. > > Could someone help us to debug this issue? > > Thanks, > Marcello > > > _______________________________________________ > 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
