Q: A container exits with code `137`. What does this specific code universally mean in the Docker ecosystem, and where should you look next?
Exit code 137 specifically means the container received a SIGKILL (signal 9) and was abruptly terminated ($128 + 9 = 137$).
#Docker #Docker #L1 #Containers #Linux #Terraform State
🎙️ Candidate Opening & Architectural Context
""During an image optimization initiative across our services, we solved this exact problem. The interviewer is testing: Exit code evaluation, OOM killer.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Advertisement
🛠️ Production Runbook & Step-by-Step Resolution
1️⃣
Production Solution & Architecture
Exit code 137 specifically means the container received a SIGKILL (signal 9) and was abruptly terminated ($128 + 9 = 137$). In 90% of Docker/Kubernetes scenarios, this means the container was violently killed by the OOM (Out Of Memory) Killer because it exceeded its allocated memory limits. *Next Steps:* I would immediately run docker inspect and check the State.OOMKilled boolean flag to confirm. Then, I would review application memory profiling and potentially increase the -m (memory limit) on the container runtime.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Exit code 137 specifically means the container received a SIGKILL (signal 9) and was abruptly terminated ($128 + 9 = 137$).."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: Exit code 137 specifically means the container received a SIGKILL (signal 9) and was abruptly t
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement