Azure Container Registry pull request fails with dial tcp lookup no such host
Question
Issue : Created a Azure Container Registry . Using Jenkins to Automate CI/CD . The image push to the repository is successful. However when we try to pull the image on the same jenkins box it fails with error :
- docker pull simplimedpoc.azurecr.io/bot-demo:latest Error response from daemon: Get https://simplimedpoc.azurecr.io/v2/ : dial tcp: lookup simplimedpoc.azurecr.io on 168.63.129.16:53: no such host
1 answers
solution1
0 2018-03-12 21:26:15
I was having a similar problem. In my case, it was because my registry was in one virtual network and the VM I was using to pull the image was in a different virtual network. I added "peering" via the portal and was able to pull images after that.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.
Related Question
Kubernetes in Azure - Unable to connect to the server: proxyconnect tcp: dial tcp: lookup http: no such host
Error response from daemon: Get https://azure/v2/: dial tcp: lookup azure: no such host
Unable to connect to the server: dial tcp: lookup <Server Location>: no such host
Azure AKS Error: Kubernetes cluster unreachable dial tcp no such host 443
Pull image Azure Container Registry - Kubernetes
Pull azure container registry image in kubernetes helm
Unable to pull image from Azure Container Registry
Azure App Service Fails to Start w/ Azure Container Registry Pull - Docker Container - Can not Find File - Works with Docker Hub
Can't pull image from Azure Container Registry - pull denied
How to pull container image from docker registry to deploy azure container
Related Tags