Diagnosing Docker Exit Code 137: Tracing OOM Kills from Container to Host
Exit code 137 means SIGKILL, usually from the kernel OOM killer. Learn to tell a too-low container limit from host memory pressure, and apply the right fix for each.
Loading…
ReadMeFeed / Community knowledge
#oom-killer
Real questions. Useful conversations. Find the people who know your stack.
docker
Preventing OOM Kills with Linux cgroups v2 memory.high
Stop relying solely on memory.max. Learn how to use Linux cgroups v2 memory.high to throttle memory-intensive processes and prevent OOM kills through proactive reclamation.
Resource Limit Behavior for Memory-Intensive Processes
Replit utilizes containerized environments to enforce CPU and RAM allocations based on the user's account tier. While the 'Resources' tab provides real-time monitoring, the behavior of the environment when a process approaches its memory ceiling remains a point of operational uncertainty. Specifically, when a memory-intensive application exceeds its allocate
replitRHEL Cgroup Memory Limits and OOM Killer Scoring Interoperability
In Red Hat Enterprise Linux (RHEL 8/9), the interaction between cgroup-based memory limits and the global Out-of-Memory (OOM) killer creates complex resource management scenarios. While the kernel uses a scoring mechanism based on resident set size (RSS) to select victim processes, the behavior shifts when memory pressure is localized within a specific cgrou
redhatWhich oom_score_adj values prevent critical service termination in cgroup v2?
In Red Hat Enterprise Linux (RHEL), the Out of Memory (OOM) Killer selects processes for termination based on a calculated score. To protect critical system services from being targeted during memory pressure, administrators can utilize the oom_score_adj interface to manually adjust a process's kill priority. When these services are isolated within cgroup v2