Kubernetes
Easy
Troubleshooting
A Kubernetes container shows reason OOMKilled with exit code 137. What does the exit code 137 tell you?
Select your answer:
Show answer and explanation
Answer: The process was killed by SIGKILL, signal 9
Explanation
A process killed by a signal reports an exit code of 128 plus the signal number, and 128 + 9 = 137. The kernel OOM killer uses SIGKILL, which can't be caught. SIGTERM would give 143, and a SIGKILL can also come from the kubelet after a grace period runs out, so check the OOMKilled reason too.
More easy Kubernetes questions
- A container restarted after an out-of-memory kill. Which field of the Kubernetes pod status records that the previous run was OOMKilled?
- A container writes files to an emptyDir volume with medium: Memory. What do those files count against?
- Which kubectl command is used to view the logs of a pod?
- What is a Pod in Kubernetes?
- What is the purpose of a Kubernetes Service?
- Which command would you use to create a deployment from a YAML file?