Hi Michael, Shouldn't "/sys/fs/cgroup/unified" be mounted by systemd to be used lxc to use cgroupv2?
Should we need to do "mount -t tmpfs cgroup /sys/fs/cgroup" for cgroupv2 as well? Will it be done systemd ? In cgroupv1, it is usually seen "/sys/fs/cgroup" mounted on tmpfs. In case of cgroupv2 unified, nothing like that is seen. df -h Filesystem Size Used Avail Use% Mounted on udev 3.4G 0 3.4G 0% /dev tmpfs 692M 1.7M 691M 1% /run /dev/sda8 125G 57G 62G 48% / tmpfs 3.4G 0 3.4G 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/sda1 96M 62M 35M 65% /boot/efi tmpfs 692M 212K 692M 1% /run/user/1000 Please note that lxc and lxcfs is malfunctioning for fresh installs (Linux coffee 5.10.0-1-amd64 #1 SMP Debian 5.10.4-1 (2020-12-31) x86_64 GNU/Linux) as well. Not sure which package is having problem. But its(lxc) not working. ======================================================== I will try the below suggestion and will update if its working. Thanks and Regards, Bharani On Tue, 2021-01-26 at 13:06 +0100, Michael Biebl wrote: > Am 26.01.21 um 12:57 schrieb [email protected]: > > > mount | grep -i cgroup > > cgroup2 on /sys/fs/cgroup type cgroup2 > > (rw,nosuid,nodev,noexec,relatime) > > > > This is intentional. See systemd's NEWS file: > > systemd (247.2-2) unstable; urgency=medium > > systemd now defaults to the "unified" cgroup hierarchy (i.e. > cgroupv2). > This change reflects the fact that cgroupsv2 support has matured > substantially in both systemd and in the kernel. > All major container tools nowadays should support cgroupv2. > If you run into problems with cgroupv2, you can switch back to the > previous, > hybrid setup by adding "systemd.unified_cgroup_hierarchy=false" to > the > kernel command line. > You can read more about the benefits of cgroupv2 at > https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html > > -- Michael Biebl <[email protected]> Mon, 21 Dec 2020 18:40:10 > +0100 > > >
