<p>I am running Kubernetes (Minikube) on my local Mac.</p>
<p>I am trying to setup a deployment with Docker image and getting the below error. But, the hello-world deployment with the Docker image &quot;gcr.io/google-samples/node-hello:1.0&quot; works as expected.</p>
<p>I am able to pull the image from a console on my local machine. Am I missing any setting here?</p>
<blockquote>
<p>&quot;Failed to pull image
&quot;docker.XYZ.com/dpace/dev/docker-service&quot;: rpc error:
code = Unknown desc = Error response from daemon: Get
https:/docker.XYZ.com/v2/: dial tcp: lookup
docker.XYZ.com on 10.0.2.3:53: read udp
10.0.2.15:59292-&gt;10.0.2.3:53: i/o timeout&quot;</p>
</blockquote>
<p>I am able to pull the image using <code>docker pull docker.XYZ.com/dpace/dev/docker-service</code> in my local machine without any auth issue. It doesn't need auth for pulling images.</p>
<p>I tried logging into Minikube VM and Docker images returns the following.</p>
<blockquote>
<p>$ docker images REPOSITORY                                    TAG<br />
IMAGE ID            CREATED             SIZE
k8s.gcr.io/kubernetes-dashboard-amd64         v1.8.1<br />
e94d2f21bc0c        3 months ago        121MB
gcr.io/google-containers/kube-addon-manager   v6.5<br />
d166ffa9201a        4 months ago        79.5MB
gcr.io/k8s-minikube/storage-provisioner       v1.8.0<br />
4689081edb10        4 months ago        80.8MB
gcr.io/k8s-minikube/storage-provisioner       v1.8.1<br />
4689081edb10        4 months ago        80.8MB
k8s.gcr.io/k8s-dns-sidecar-amd64              1.14.5<br />
fed89e8b4248        5 months ago        41.8MB
k8s.gcr.io/k8s-dns-kube-dns-amd64             1.14.5<br />
512cd7425a73        5 months ago        49.4MB
k8s.gcr.io/k8s-dns-dnsmasq-nanny-amd64        1.14.5<br />
459944ce8cc4        5 months ago        41.4MB k8s.gcr.io/echoserver<br />
1.4                 a90209bb39e3        21 months ago       140MB gcr.io/google_containers/pause-amd64          3.0<br />
99e59f495ffa        22 months ago       747kB k8s.gcr.io/pause-amd64<br />
3.0                 99e59f495ffa        22 months ago       747kB gcr.io/google-samples/node-hello              1.0<br />
4c7ea8709739        23 months ago       644MB</p>
</blockquote>
<p>Though the images are there, when I try to pull the existing image, it fails with the below error.</p>
<blockquote>
<p>$ docker pull gcr.io/google-samples/node-hello:1.0 Error response from
daemon: Get <a href="https://gcr.io/v2/" rel="nofollow noreferrer">https://gcr.io/v2/</a>: dial tcp: lookup gcr.io on
10.0.2.3:53: read udp 10.0.2.15:44023-&gt;10.0.2.3:53: i/o timeout</p>
</blockquote>
<p>When I try &quot;docker login docker.XYZ.com&quot;, it prompts me to enter the credential. It throws the below error after entering the password. Same error while trying to pull the image also.</p>
<blockquote>
<p>&quot;Error response from daemon: Get <a href="https://docker.XYZ.com/v2/" rel="nofollow noreferrer">https://docker.XYZ.com/v2/</a>: dial tcp:
lookup docker.XYZ.com on 10.0.2.3:53: read udp
10.0.2.15:41849-&gt;10.0.2.3:53: i/o timeout&quot;</p>
<p>The command &quot;curl google.com&quot; also not working.  &quot;Could not resolve
host: google.com&quot;</p>
</blockquote>
<p>Any setting to be done inside Minikube VM. I use VirtualBox.</p>

<p>Looks like DNS in your minikube is broken, that's why you cannot pull anything.</p>

<p>Here is an <a href="https://github.com/kubernetes/minikube/issues/2302" rel="nofollow noreferrer">Issue on Github</a> with the similar problem.</p>

<p>Try to update your minikube and your hypervisor (in most of cases it is Virtualbox) to the last version (check <a href="https://github.com/kubernetes/minikube/releases" rel="nofollow noreferrer">here</a>) and recreate a cluster, it should help.</p>
