-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support host side cgroups v2 #927
Comments
@jodh-intel was this already fixed? |
This could be more important very soon. Ubuntu 21.10 is going to ship with cgroups v2 enabled by default: https://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-21.10-systemd-cgroup |
Is there any news or a roadmap here? Also Debian 11 "bullseye" now has cgroups v2 as default. Containerd runs in a "mountpoint does not exist" (also with setting sandbox_cgroup_only=true). Thx & regards |
Arch and all derivates (EndeavourOS, Manjaro, Garuda) have also per default cgroup v2. |
What is blocking this from fixed? |
@jodh-intel we are joining a summer code and can I assign this one to others if you are not started yet? |
Hi @liubin - yes, please do! ;) I was not involved in discussions on this being assigned to me, and don't have the time to look at it. |
:( Manjaro no bueno due to this it seems! |
This issue should have been closed when #4397 landed (issue #3073). See: https://github.com/kata-containers/kata-containers/blob/main/docs/design/host-cgroups.md Closing this issue, but I've raised #6259 to fix |
Problem
The runtime doesn't support cgroups v2 on the host.
Consequence
This means we cannot run on F31 and F32, which default to cgroups v2 only without the user performing surgery on their system (reverting to cgroups v1 by changing bootloader stuff and rebooting - yikes!)
Related:
The text was updated successfully, but these errors were encountered: