Exit code 137 doesn't mean it ran out of memory
This story is from 2026-11-16. It is preserved in the archive; the latest stories are on the live feed.
137 just means the process got SIGKILL. the OOM killer sends that, but so does a failed liveness probe, a node draining, or someone running kubectl delete at the wrong moment. so before chasing a leak, run kubectl describe pod and look at the last state. OOMKilled is spelled out there when it's rea…
Read the full story at DEV Community — AI ↗
Timeline · 1 report
- 2026-11-16 16:34 · DEV Community — AI
Exit code 137 doesn't mean it ran out of memory