KBY Technologies Logo
ImagePullBackOff

Kubernetes ImagePullBackOff

The node cannot retrieve a container image and is delaying subsequent pull attempts.

kubelet image manager and container runtimeImage deliveryhigh
Exact message
Back-off pulling image

Also 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
Evidence before intervention

First diagnostic checks

1

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>
2

Verify the resolved image

Confirm the complete registry, repository, tag or digest in the deployed Pod specification.

3

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.

Engineering signal

Follow Kubernetes failures and fixes

One useful weekly email with new error references, tools, integration notes and production lessons. No daily noise.