Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bug： OOMKilled event not reported to containerd #142

Open
abel-von opened this issue May 9, 2023 · 0 comments
Open

Bug： OOMKilled event not reported to containerd #142

abel-von opened this issue May 9, 2023 · 0 comments
Labels
T-bug Something isn't working

Comments

@abel-von
Copy link
Contributor

abel-von commented May 9, 2023 •
edited

For shim of golang version, containerd can receive an event of OOMKilled when a container is oom killed. the reason of container exit is set to "OOMKilled". kubernetes can also get this reason the show it to user. This is a useful information somtimes, because otherwise users don't know why their container exit, and can not find any clues.
@mxpv mxpv added the T-bug Something isn't working label Aug 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
T-bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mxpv @abel-von