Unverified50% confidenceFactExact time
当容器内存超过 Pod 资源限制时，Linux 内核的 OOM Killer 会向容器主进程发送不可捕获的 SIGKILL 信号，Kubernetes 将 Pod 标记为 OOMKilled 状态，退出码为 137
1
Sources
50%
Confidence
Long-term
Relevance
8/5/2026
First Seen
Sources
Related Claims
Unverified在Linux进程信号体系中，SIGTERM（信号15）是标准终止请求且进程可捕获，SIGINT（信号2）为Ctrl+C，SIGKILL（信号9）绕过进程由内核强制回收资源且无法被捕获或忽略62% similarUnverifiedIn Kubernetes, kubelet calls the container runtime (such as containerd), which creates the container process via runc, potentially going through a pause container to maintain the Pod's network namespace.61% similarVerified容器技术（以Docker为代表）利用Linux内核的namespace机制实现进程、网络、文件系统隔离，借助cgroups限制CPU、内存等资源用量61% similarUnverifiedKubernetes exposes GPUs as schedulable resources through the Device Plugin mechanism; once a Pod requests a GPU, it exclusively holds that resource until the Pod is destroyed.60% similarUnverified容器依赖Linux的Namespace（资源隔离）和Cgroup（资源配额限制）两大机制，配合Seccomp过滤系统调用59% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/692497API
curl https://kongchang.com/api/v1/knowledge/claims/692497MCP
get_claim(id=692497)