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.

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

Container freezing instead of OOM #759

Closed
janmuennich opened this issue Apr 16, 2024 · 3 comments · Fixed by #760
Closed

Container freezing instead of OOM #759

janmuennich opened this issue Apr 16, 2024 · 3 comments · Fixed by #760
Assignees
Labels
Bug Confirmed to be a bug Easy Good for new contributors
Milestone

Comments

@janmuennich
Copy link

Required information

  • Distribution: Ubuntu
  • Distribution version: 22.04
  • The output of "incus info" or if that fails:
    • Kernel version: 5.15.0-92-generic
    • Incus version: 6.0 LTS
    • Storage backend in use: ZFS

Issue description

On LXD since 5.0.3 LTS we regularly see that processes in containers are not killed when the configured memory limit is reached (OOM). This seems to be the same issue as canonical/lxd#13147

I now tried to reproduce an OOM situation in a container with Incus 6.0 which also led to a freeze instead of some processes killed.

Is Incus affected by the same bug ?

Steps to reproduce

  1. Configure a memory limit with lxc config set limits.memory 1GiB
  2. Create an OOM situation with stress-ng or a similar tool or with regular applications
  3. Container freezes and load average goes up on host system
stgraber added a commit to stgraber/incus that referenced this issue Apr 16, 2024
@stgraber stgraber self-assigned this Apr 16, 2024
@stgraber stgraber added Bug Confirmed to be a bug Easy Good for new contributors labels Apr 16, 2024
@stgraber stgraber added this to the incus-6.1 milestone Apr 16, 2024
@janmuennich
Copy link
Author

Thanks. Is there any workaround to correctly set the hard memory limit in the meantime?

@stgraber
Copy link
Member

If you're using the Zabbly packages, just apply your updates as the fix was backported right after it landed.

Otherwise the two options I can see as workarounds are:

  • Give more RAM until the issue is resolved
  • Reboot your system in cgroup1 mode until the issue is resolved

@janmuennich
Copy link
Author

Amazing! I thought I had to wait for 6.0.1 ;)

stgraber added a commit that referenced this issue May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Confirmed to be a bug Easy Good for new contributors
Development

Successfully merging a pull request may close this issue.

2 participants