Error AtlasError Documentation and Resolution
Back to search

GKE

GKE pod failed with ErrImagePull

ErrImagePull

A Google Kubernetes Engine pod could not pull the required container image, so Kubernetes reported ErrImagePull before backing off additional attempts.

ErrImagePullcontainers

Observed message

ErrImagePull

Why it happens

  • The image name, tag, or registry path is incorrect.
  • The cluster lacks permission to pull from the target registry.
  • Network, DNS, or registry connectivity problems are blocking the image pull.

How to fix it

  1. Verify the image reference exactly as used in the workload manifest.
  2. Confirm the node or workload identity can access the image registry.
  3. Review network access, DNS, and registry reachability from the cluster.

Official reference

Google Cloud: Troubleshoot image pulls in GKE

Related errors

ImagePullBackOffGKE pod failed to pull its container imageCrashLoopBackOffGKE pod is stuck in CrashLoopBackOff0/1 nodes are available: 1 node(s) didn't have free ports for the requested pod ports.GKE could not schedule the pod because nodes did not have free requested pod ports401 UnauthorizedGKE image pull failed with 401 Unauthorized

Explore more

containersBrowse more containers errors
GKE ErrImagePull: causes and fixes | Error Atlas