Hi Thorsten, Le vendredi 28 août 2020 à 08:28 +0200, Thorsten Kukuk a écrit :
On Thu, Aug 27, Sébastien 'sogal' Poher wrote:
Hi,
On a fresh MicroOS install with podman, when I want to set memory limit for a container (using the -m flag) I get the following error:
Error: container_linux.go:367: starting container process caused: process_linux.go:459: container init caused: process_linux.go:422: setting cgroup config for procHooks process caused: cannot set memory limit: container could not join or create cgroup: OCI runtime error
I am not able to understand the nature of the error. Searching around, I found similar issue where adding cgroup_enable=memory parameter to boot settings in Grub might solve the issue. Is that correct ?
I don't know.
If so, what is the proper way to update Grub config on a RO filesystem ?
vi /etc/default/grub transactional-update grub.cfg -> reboot
should do it.
Thank you for your answer about Grub. The issue with memory limit is still here. The same command works on Fedora where: podman info | grep -i cgroup cgroupVersion: v2 whereas in MicroOS: podman info | grep -i cgroup cgroupVersion: v1 Could this issue be related to cgroup version ? Will MicroOS use cgroup v2 by default in a near future ? -- Sébastien 'sogal' Poher
When there's no more room at school, the dumb will walk the Earth! -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org