Kubernetes ImagePullBackOff
The node cannot retrieve a container image and is delaying subsequent pull attempts.
Back-off pulling imageAlso searched as: ErrImagePull · ImagePullBackOff
What it means
The image reference, registry authentication, network path, platform architecture, or registry availability prevented the runtime from obtaining the image.
Typical trigger conditions
- Incorrect repository or tag
- Missing or invalid imagePullSecret
- Registry rate limit or outage
- Node DNS, proxy or egress failure
First diagnostic checks
Read the pull event
The event normally includes the registry response that distinguishes not-found, unauthorized and transport failures.
kubectl describe pod <pod> -n <namespace>
Verify the resolved image
Confirm the complete registry, repository, tag or digest in the deployed Pod specification.
Check pull credentials
Verify imagePullSecrets exist in the same namespace and are attached to the Pod or ServiceAccount.
Version and platform notes
Credential-provider mechanisms differ between managed platforms and kubelet versions; use the cluster provider's supported method.
Related engineering templates
Follow Kubernetes failures and fixes
A useful digest about twice a week with new error references, tools, integration notes and production lessons. No daily noise.