Kubernetes
Nov 15, 2025 5 min read

Fix ImagePullBackOff and ErrImagePull in Kubernetes

Why ImagePullBackOff happens and how to fix it — registry auth, wrong tags, and private images.

Problem

A pod stays in `ImagePullBackOff` or `ErrImagePull`. The container image cannot be pulled from the registry.

Root cause

  • Image tag does not exist (typo or moved tag).
  • Private registry without an `imagePullSecret`.
  • Expired registry credentials.
  • Node cannot reach the registry (DNS, firewall, airgap).

Solution

Confirm the exact error

bash
kubectl describe pod <pod> | grep -A2 'Failed'

Create a pull secret

bash
kubectl create secret docker-registry regcred \
  --docker-server=registry.example.com \
  --docker-username=USER \
  --docker-password=TOKEN

Reference it in the Deployment

yaml
spec:
  imagePullSecrets:
    - name: regcred
  containers:
    - name: api
      image: registry.example.com/api:1.4.2

Frequently asked questions

Related fixes

Weekly digest

One DevOps fix in your inbox each week

Short, practical, no fluff. Real errors, real fixes — straight from production postmortems.