https://rancher.com/ logo
Title
h

handsome-painter-48813

10/07/2022, 10:48 AM
Hello, I upgraded debian from 10 to 11 and I can't start k3s server:
failed to find cpuset cgroup (v2)
k3s check-config:
Generally Necessary:
- cgroup hierarchy: cgroups V2 mounted, cpu|cpuset|memory controllers status: bad (fail)
    (for cgroups V1/Hybrid on non-Systemd init see <https://github.com/tianon/cgroupfs-mount>)
- /usr/sbin/apparmor_parser
apparmor: enabled and tools installed
I already set
GRUB_CMDLINE_LINUX="systemd.unified_cgroup_hierarchy=0"
And it does not work 😕
l

late-needle-80860

10/07/2022, 10:58 AM
What version of K3s?
h

handsome-painter-48813

10/07/2022, 11:13 AM
k3s version v1.25.2+k3s1 (53c268d8)
go version go1.19.1
I read that it should work with cgroups2
l

late-needle-80860

10/07/2022, 12:40 PM
Yeah I believe so as well
h

handsome-painter-48813

10/07/2022, 12:42 PM
Thanks for help, I got it working with `/etc/default/grub`:
GRUB_CMDLINE_LINUX="systemd.unified_cgroup_hierarchy=0"
and then:
update-grub
reboot now
🎯 1
l

late-needle-80860

10/07/2022, 12:42 PM
Nice … so it simply wasn’t enabled or what? cgroup v2?
h

handsome-painter-48813

10/07/2022, 12:43 PM
This
systemd.unified_cgroup_hierarchy=0
enables cgroups v1
Cgroups v2 is enabled by default in Debian 11, so k3s does not work
l

late-needle-80860

10/07/2022, 1:37 PM
Aaah sheize … that’s what it means of course. But, is it really a K3s specific thing … and not actually any Kubernetes distro?
c

creamy-pencil-82913

10/07/2022, 4:31 PM
the problem is that you need to be in either v1 or v2(unified) mode. Hybrid mode (where some are v1 and some are v2) does not work. In your case it sounds like the cpuset controller was still on v1 and the rest were on v2.
l

late-needle-80860

10/07/2022, 4:34 PM
Aaaah yes. Makes sense.