Kir Kolyshkin a675b5ebea cgroupv2: don't try to set kmem for systemd case ... To the best of my knowledge, it has been decided to drop the kernel memory controller from the cgroupv2 hierarchy, so "kernel memory limits" do not exist if we're using v2 unified. So, we need to ignore kernel memory setting. This was already done in non-systemd case (see commit 88e8350de), let's do the same for systemd. This fixes the following error: > container_linux.go:349: starting container process caused "process_linux.go:306: applying cgroup configuration for process caused \"open /sys/fs/cgroup/machine.slice/runc-cgroups-integration-test.scope/tasks: no such file or directory\"" Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>		2020-03-25 20:00:23 -07:00
..
apply_nosystemd.go	libcontainer: add method to get cgroup config from cgroup Manager	2019-12-17 22:46:03 +00:00
apply_systemd.go	vendor: update go-systemd and godbus	2020-03-16 13:26:03 +09:00
unified_hierarchy.go	cgroupv2: don't try to set kmem for systemd case	2020-03-25 20:00:23 -07:00