Help! Can't Pull Images After Rebooting My Cluster

September 10, 2025 2 answers
Asked by SparkySunshine42
I recently had to move my entire cluster, and after bringing everything back online, I'm running into issues pulling images. For instance, when I tried to pull the homepage container, I got the following error: "Failed to pull image

Answers

TechieDan007
It sounds like a network issue rather than a credential problem. Can you check if the host can reach the IP and port directly? That might give you some clues about whatโ€™s going on.

SparkySunshine42: I thought so too, but other pods on the same node can pull images just fine. I'm using Talos Linux, so I canโ€™t shell into the pods directly. I even tried deploying a debug pod with the ping command, but I couldn't pull the image. Any ideas on how I can check connectivity? Iโ€™m also seeing errors in the Talos dashboard about not being able to add a route, along with I/O timeouts for "discovery.talos.dev".

Reply to this answer
CloudExplorer88
You might want to try running `kubectl describe node ` as a troubleshooting step. My guess is that your CNI (Container Network Interface) might be having issues. Restarting the Cilium deployment in the kube-system namespace with `kubectl rollout restart deployment cilium -n kube-system` could also help.
Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions