Closed CameronNemo closed 4 years ago
I can reproduce this with plain LXC too... it appears that cpuset.cpus
is unset for the lxc cgroups.
root@ceci /s/f/c/cpuset# head lxc.*/cpuset.{mems,cpus}
==> lxc.monitor/cpuset.mems <==
0
==> lxc.pivot/cpuset.mems <==
0
==> lxc.monitor/cpuset.cpus <==
==> lxc.pivot/cpuset.cpus <==
I believe that's a liblxc bug that's been fixed upstream for a few months but isn't yet in any released version of liblxc.
One workaround can be found in the lxd snap packaging here:
https://github.com/lxc/lxd-pkg-snap/blob/latest-edge/snapcraft/commands/daemon.start#L263
Stéphane, do you happen to know the LXC commit(s) fixing this? Is it possible for me to backport it? I would need to tell LXC users to add that snippet to their rc.local
otherwise. (I am just adding it to the runit run file for LXD).
https://github.com/lxc/lxd-pkg-snap/blob/latest-candidate/snapcraft.yaml#L530
That's the list of commits we currently cherry pick for the snap, including the needed cgroups fixes.
Required information
lxc info --show-log local:chief-gull
Issue description
Launching a container fails.
Steps to reproduce
lxd init
lxc launch images:voidlinux
Tested with multiple images.