You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Configure a memory limit with lxc config set limits.memory 1GiB
Create an OOM situation with stress-ng or a similar tool or with regular applications
Container freezes and load average goes up on host system
The text was updated successfully, but these errors were encountered:
stgraber
added a commit
to stgraber/incus
that referenced
this issue
Apr 16, 2024
Required information
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
lxc config set limits.memory 1GiB
stress-ng
or a similar tool or with regular applicationsThe text was updated successfully, but these errors were encountered: