This message was deleted.
# k3sa
adamant-kite-43734
10/07/2022, 10:48 AMThis message was deleted.
l
late-needle-80860
10/07/2022, 10:58 AMWhat version of K3s?
h
handsome-painter-48813
10/07/2022, 11:13 AM Copy code
k3s version v1.25.2+k3s1 (53c268d8)
go version go1.19.1l
late-needle-80860
10/07/2022, 12:40 PMYeah I believe so as well
h
handsome-painter-48813
10/07/2022, 12:42 PMThanks for help, I got it working with `/etc/default/grub`:
Copy code
GRUB_CMDLINE_LINUX="systemd.unified_cgroup_hierarchy=0" Copy code
update-grub
reboot now🎯 1
l
late-needle-80860
10/07/2022, 12:42 PMNice … so it simply wasn’t enabled or what? cgroup v2?
h
handsome-painter-48813
10/07/2022, 12:43 PMThis
Copy code
systemd.unified_cgroup_hierarchy=0handsome-painter-48813
10/07/2022, 12:44 PMCgroups v2 is enabled by default in Debian 11, so k3s does not work
l
late-needle-80860
10/07/2022, 1:37 PMAaah 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 PMthe 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 PMAaaah yes. Makes sense.
220 Views