DEV Community

Deep Fix
Deep Fix

Posted on

How to Resolve Docker Container CrashLoopBackOff – Step‑by‑Step Guide for Kubernetes

#docker #kubernetes #troubleshooting #devops

Resolving Docker Container CrashLoopBackOff

Docker containers orchestrated by Kubernetes may enter a CrashLoopBackOff state, causing downtime and frustration. In this guide we walk through the most common root causes and provide step‑by‑step commands to get your pods running again.

1. Verify the pod status 

kubectl get pods
Enter fullscreen mode Exit fullscreen mode

Identify the pod showing CrashLoopBackOff and note its name.

2. Inspect events and description 

kubectl describe pod <pod-name>
Enter fullscreen mode Exit fullscreen mode

Look for Last State, Reason, and any Event messages that hint at the failure.

3. View container logs 

kubectl logs <pod-name> -c <container-name>
Enter fullscreen mode Exit fullscreen mode

If the container exits quickly, add --previous to see the logs from the last run:

kubectl logs <pod-name> -c <container-name> --previous
Enter fullscreen mode Exit fullscreen mode

4. Common culprits & fixes

Issue Symptom Fix
Wrong command or entrypoint exec: "myapp": executable file not found Update command: or entrypoint: in the pod spec.
Missing environment variable panic: environment variable XYZ not set Add the variable under env: in the deployment.
OOMKilled OOMKilled in events Increase resources.limits.memory or optimize the app.
Crash due to failing health probe Readiness probe failed Adjust initialDelaySeconds or fix the probe endpoint.

Example: Fixing a missing env var 

apiVersion: apps/v1
kind: Deployment
metadata:
  name: myapp
spec:
  replicas: 2
  template:
    spec:
      containers:
      - name: myapp
        image: myrepo/myapp:1.0
        env:
        - name: DATABASE_URL
          value: "postgres://user:pass@db:5432/mydb"
Enter fullscreen mode Exit fullscreen mode

Example: Updating the Dockerfile entrypoint 

FROM golang:1.22-alpine AS builder
WORKDIR /app
COPY . .
RUN go build -o myapp .

FROM alpine:latest
COPY --from=builder /app/myapp /usr/local/bin/myapp
# Correct entrypoint
ENTRYPOINT ["/usr/local/bin/myapp"]
Enter fullscreen mode Exit fullscreen mode

5. Re‑apply the corrected manifest 

kubectl apply -f deployment.yaml
Enter fullscreen mode Exit fullscreen mode

Watch the rollout status:

kubectl rollout status deployment/myapp
Enter fullscreen mode Exit fullscreen mode

6. When all else fails

  • Delete the pod to let the ReplicaSet create a fresh instance: 
kubectl delete pod <pod-name>
Enter fullscreen mode Exit fullscreen mode
  • Use a debugging sidecar or kubectl exec into a running container to inspect the filesystem.

Ready to automate the fix? Download the pre‑configured script here, Get the complete patch tool, or Access the full repository fix at our GitHub Pages site.

Top comments (0)