K
Q

Kubectl throws ImagePullBackOff Error while creating deployment via minikube

12/9/2019

Trying to create a deployment from an image

kubectl create deployment hello-minikube --image=k8s.gcr.io/echoserver:1.10

and then do kubectl get pods and check the logs of hello-minikube pod using

kubectl pod describe <pod-name> throws following error

  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  <unknown>          default-scheduler  Successfully assigned default/hello-minikube-797f975945-dmq26 to minikube
  Warning  Failed     42s                kubelet, minikube  Failed to pull image "k8s.gcr.io/echoserver:1.10": rpc error: code = Unknown desc = Error response from daemon: Get https://k8s.gcr.io/v2/: dial tcp: lookup k8s.gcr.io on 192.168.64.1:53: read udp 192.168.64.3:56747->192.168.64.1:53: read: connection refused
  Warning  Failed     27s                kubelet, minikube  Failed to pull image "k8s.gcr.io/echoserver:1.10": rpc error: code = Unknown desc = Error response from daemon: Get https://k8s.gcr.io/v2/: dial tcp: lookup k8s.gcr.io on 192.168.64.1:53: read udp 192.168.64.3:48279->192.168.64.1:53: read: connection refused
  Normal   BackOff    16s (x2 over 42s)  kubelet, minikube  Back-off pulling image "k8s.gcr.io/echoserver:1.10"
  Warning  Failed     16s (x2 over 42s)  kubelet, minikube  Error: ImagePullBackOff
  Normal   Pulling    4s (x3 over 42s)   kubelet, minikube  Pulling image "k8s.gcr.io/echoserver:1.10"
  Warning  Failed     4s (x3 over 42s)   kubelet, minikube  Error: ErrImagePull
  Warning  Failed     4s                 kubelet, minikube  Failed to pull image "k8s.gcr.io/echoserver:1.10": rpc error: code = Unknown desc = Error response from daemon: Get https://k8s.gcr.io/v2/: dial tcp: lookup k8s.gcr.io on 192.168.64.1:53: read udp 192.168.64.3:50616->192.168.64.1:53: read: connection refused
-- Shivani Singhal
docker
go
kubectl
kubernetes
minikube

Similar Questions

ArangoDB init container fails on minikube
Can we store the TLS certificates in Azure Key vault as a secret and use the same in Ingress in Azure Kubernetes service
why not create multiple containers instead of using kubernetes
Providing DNS for Kubernetes services with bare metal load balancer
Restart pod when spring vault renew token does not work
Use Application Load Balancers | Helm chart | AWS
openshift 3.12 websocket ERR_CONNECTION_ABORTED
How to enable Alert manager pick alert manager configs from a new kubernetes namespace?

2 Answers

12/12/2019

From the events it looks like the call to a DNS server at 192.168.64.1:53 to resolve k8s.gcr.io is failing. Check if there's a DNS server running at that IP. It may be configured in /etc/resolv.conf (if Linux) on the minikube host.

-- gears
Source: StackOverflow
12/9/2019

This error can be solved using :

  1. Check whether any docker machine is running or not by docker-machine ls

  2. If no machine exist, then create one using docker-machine create <machine-name>

  3. Then get this machine IP using docker-machine ip <machine-name>

  4. Then first delete any existing minikube cluster using minikube delete and start again using minikube start --vm-driver="virtualbox" --insecure-registry="docker-machine IP":80

  5. Then run kubectl create deployment hello-minikube --image=k8s.gcr.io/echoserver:1.10 and check the logs, it will show image pulled successfully.

-- Shivani Singhal
Source: StackOverflow