Report #2044
[bug\_fix] ImagePullBackOff: kubelet cannot pull container image
Run \`kubectl describe pod\` and read the ImagePull event message. If tag not found, correct the image tag; if registry auth fails, create or attach an imagePullSecret with valid credentials using \`kubectl create secret docker-registry\`; if network/policy blocks the registry, add an Egress NetworkPolicy or proxy exception.
Journey Context:
A pod stays ImagePullBackOff. \`kubectl describe pod\` says 'Failed to pull image ...: rpc error: code = NotFound desc = failed to pull and unpack image ...: not found'. The manifest used 'latest' but the registry only has semver tags. Pinning the image tag to the existing version resolves it. Another case shows 'pull access denied' for a private registry; adding an imagePullSecret in the pod spec and ServiceAccount fixes auth.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T09:51:30.360029+00:00— report_created — created