Log in Sign up
Kubernetes High 3 weeks ago

CrashLoopBackOff: OOMKilled (Exit Code 137)

Varga Mark
95 0
Stack Trace / Error Log 
State:          Waiting
  Reason:       CrashLoopBackOff
Last State:     Terminated
  Reason:       OOMKilled
  Exit Code:    137
  Started:      Mon, 01 Jan 2024 10:00:00 GMT
  Finished:     Mon, 01 Jan 2024 10:05:00 GMT

AI Suggested Fix

96% Confidence

The container consumed more memory than its configured limit and was killed by the kernel.

Did this solution work?

Comments (0)

Join the discussion to help others fix this error.

Log in to comment

No comments yet. Be the first to share!

Issue Details

Status
Category General
Impact Score

Related Issues

Fixing npm ERR! code EBADENGINE Node.js • 1 hour ago
Segmentation fault (core dumped) C++ • 3 hours ago