Kubernetes - Fundamentals
A node's kubelet is running but pods are stuck in Pending state. Logs show 'Failed to pull image'. What is the most likely cause?
A node's kubelet is running but pods are stuck in Pending state. Logs show 'Failed to pull image'. What is the most likely cause?
medium📝 Troubleshoot Q7 of 15
Step-by-Step Solution
Solution:
Step 1: Understand error meaning
'Failed to pull image' means container runtime cannot download the container image.Step 2: Identify cause
This usually happens if the container runtime cannot reach the image registry or lacks credentials.Final Answer:
Container runtime cannot access the image registry -> Option CQuick Check:
Image pull failure = container runtime registry access issue [OK]
Quick Trick: Image pull errors mean container runtime registry access problem [OK]
Common Mistakes:
- Blaming kube-proxy
- Assuming etcd affects image pull
- Ignoring network or auth issues
Master "Fundamentals" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes