>But the issue with OOM continue, for example some minutes ago OOM-Killer has
>been executed, writing in syslog:
>[...]
>and killing a process outside the container that has invoked it.
Dear Davide,
If it's not from a container, may this happens from the OOM-Killer of the host
context?
And jus
Hi,
I've a Centos 6 server with custom kernel 3.3.6 compiled (config
from centos) that contains about 40 lxc.
I have compiled the kernel to resolve (unsuccessfully) an OOM issue. With:
lxc.cgroup.memory.limit_in_bytes = 500M
lxc.cgroup.memory.memsw.limit_in_bytes = 500M
lxc.cgroup.memory.oom_contr
