-
Notifications
You must be signed in to change notification settings - Fork 211
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
CgroupV2 support #111
Comments
As highlighted in NVIDIA/nvidia-docker#1447 this is now breaking default debian sid/testing for lack of at least |
@lissyx Thank you for printing out the crux of the issue. That said, this rearchitecting effort will take at least another 9 months to complete. I'm curious what the impact is (and how difficult it would be to add |
I have no idea, my knowledge of cgroups is really limited, I only investigated because I ran into the issue and it was blocking me. For the moment, I'm relying on the |
So, I've seen two very different approaches to work around the current lack of cgroup v2 support:
The latter is simpler (no kernel param mods and reboot) but I've found very little discussion of the rationale for choosing one option over the other. Any advice? In case it would matter, I'm doing this to get rootless containers (docker-rootless - version 20.10.3) running under Ubuntu 18.04 (kernel 4.15.0-135-generic) with libnvidia-container version 1.3.1. |
Speaking for myself, disabling |
I'd also like to mention that this affects anyone running buster-backports now also. |
@klueska
|
As a temporary workaround, this helps:
Append your devices to docker run: |
We now have an RC of libnvidia-container out that adds support for If you would like to try it out, make sure and add the For DEBs
For RPMs
|
Is there a estimate for v1.8.0 being released? |
@PhilippHomann we are preparing the |
|
Release notes here: |
Recently, I test containerd+nvidia-container-runtime in kernal 5.4 and cgroupv2, but I find nvidia-container-cli can not run successfully because of errors as bellow shows
Is it planned to support cgroupv2?
The text was updated successfully, but these errors were encountered: