<p>The error indicates a DNS resolution issue preventing Kubelet from pulling the <code>busybox:1.28</code> image. To resolve this, first, check that <code>/etc/resolv.conf</code> is correctly configured with a functional DNS server. Next, ensure your node has internet access and can reach <code>registry-1.docker.io</code> by testing the connection with <code>curl https://registry-1.docker.io/v2/</code>. Restart Kubelet using <code>sudo systemctl restart kubelet</code> to address any transient issues, and if your DNS server is local (127.0.0.53), try flushing the DNS cache or restarting the DNS service to restore proper DNS functionality.</p>

CC BY-SA 4.0
2024-08-27T11:56:05.273Z
2024-08-27T11:56:05.273Z
lostmarien
<p>I'm learning kubernetes and I installed kube cluster with kubeadm. and I wanted to install the counter pod. but I get the following error. can you help me ?</p>
<p>Events:
Type     Reason   Age                  From     Message</p>
<hr />
<p>Warning  Failed   51m (x135 over 8h)   kubelet  (combined from similar events): Failed to pull image &quot;busybox:1.28&quot;: failed to pull and unpack image &quot;docker.io/library/busybox:1.28&quot;: failed to resolve reference &quot;docker.io/library/busybox:1.28&quot;: failed to do request: Head &quot;https://registry-1.docker.io/v2/library/busybox/manifests/1.28&quot;: dial tcp: lookup registry-1.docker.io on 127.0.0.53:53: read udp 127.0.0.1:40971-&gt;127.0.0.53:53: i/o timeout
Normal   BackOff  86s (x2172 over 8h)  kubelet  Back-off pulling image &quot;busybox:1.28&quot;</p>

CC BY-SA 4.0
2024-08-29T02:50:15.767Z
Hi there, welcome to Stackoverflow! Can you post the pod yaml please? You can surround it in ``` backticks so it's properly formatted. The more context you provide the easier it will be for people to answer your question and the less chance your post will be downvoted (I'm not the one downvoting you, just giving a friendly tip )
Almenon
<docker><kubernetes><containers><kubectl>
I can't run a pod after installing a cluster
kmaraz
# I can't run a pod after installing a cluster

(Asked by: username_0 on 2024-08-23)

I'm learning kubernetes and I installed kube cluster with kubeadm. and I wanted to install the counter pod. but I get the following error. can you help me ?

Events:
Type Reason Age From Message

---

Warning Failed 51m (x135 over 8h) kubelet (combined from similar events): Failed to pull image "busybox:1.28": failed to pull and unpack image "docker.io/library/busybox:1.28": failed to resolve reference "docker.io/library/busybox:1.28": failed to do request: Head "https://registry-1.docker.io/v2/library/busybox/manifests/1.28": dial tcp: lookup registry-1.docker.io on 127.0.0.53:53: read udp 127.0.0.1:40971->127.0.0.53:53: i/o timeout
Normal BackOff 86s (x2172 over 8h) kubelet Back-off pulling image "busybox:1.28"

**Tags:** docker, kubernetes, containers, kubectl

> **Comments:**
> **username_1**: Hi there, welcome to Stackoverflow! Can you post the pod yaml please? You can surround it in ``` backticks so it's properly formatted. The more context you provide the easier it will be for people to answer your question and the less chance your post will be downvoted (I'm not the one downvoting you, just giving a friendly tip )  

---

## 1 answers

### Answer by username_2 on 2024-08-27. Score: 0

The error indicates a DNS resolution issue preventing Kubelet from pulling the `busybox:1.28` image. To resolve this, first, check that `/etc/resolv.conf` is correctly configured with a functional DNS server. Next, ensure your node has internet access and can reach `registry-1.docker.io` by testing the connection with `curl https://registry-1.docker.io/v2/`. Restart Kubelet using `sudo systemctl restart kubelet` to address any transient issues, and if your DNS server is local (127.0.0.53), try flushing the DNS cache or restarting the DNS service to restore proper DNS functionality.


---

