ImagePullBackOff in Kubernetes: 12 Causes and How to Fix Each
ImagePullBackOff is not the error. It is the kubelet telling you that it already failed to pull your container image several times and is now waiting before it tries again, so the real message is one line above it in the pod events. The pull happens on the node , using the node's DNS, the node's network path, and the credentials you handed the kubelet - not from the machine you ran kubectl apply on. That single fact explains most of the confusing cases: the image pulls fine on your laptop and still fails in the cluster. This page gives you the one command that reveals the actual failure, the fastest fix for the common case, then 12 distinct causes - wrong tag, missing or misplaced pull secret, Docker Hub rate limits, expiring registry tokens, architecture mismatch, blocked egress, private CA, full disk - each with a reproduction, the corrected lines, and a way to confirm it is really fixed. Error STATUS: ImagePullBackOff, preceded in the pod events by: Warning Failed...