Error AtlasError Documentation and Resolution
Back to search

GKE

GKE pod is stuck in CrashLoopBackOff

CrashLoopBackOff

A Google Kubernetes Engine workload is repeatedly crashing and restarting, so Kubernetes backed off further restarts and reported CrashLoopBackOff.

CrashLoopBackOffcontainers

Observed message

CrashLoopBackOff

Why it happens

  • The container process exits shortly after startup.
  • Readiness or liveness probes are misconfigured and causing restarts.
  • The workload is failing because of configuration, missing dependencies, or resource limits.

How to fix it

  1. Inspect pod logs and previous container logs to find the immediate crash reason.
  2. Review startup commands, environment variables, and mounted configuration.
  3. Check probes and resource settings so the workload has enough time and capacity to start.

Official reference

Google Cloud: Troubleshoot GKE workloads

Related errors

ImagePullBackOffGKE pod failed to pull its container imageErrImagePullGKE pod failed with ErrImagePull0/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 CrashLoopBackOff: causes and fixes | Error Atlas