Skip to content
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

Devices support #242

Open
mythi opened this issue Sep 8, 2021 · 2 comments
Open

Devices support #242

mythi opened this issue Sep 8, 2021 · 2 comments
Labels
question Further information is requested

Comments

@mythi
Copy link

mythi commented Sep 8, 2021

@AkihiroSuda I have a question about the KEP. It says:

Device controller cannot be supported as well, but it is not a huge deal, because non-root users
don't have permission to access insecure devices anyway.

What is the problem with the device controller? I've been working on getting non-root containers + devices to work in the "non-rootless "mode and would like to understand what is needed for the rootless mode.

I understand the UID/GID for permissions but it's not clear why the eBPF device controller cannot be supported (is it more than capabilities, e.g. CAP_BPF?)

I think it is a valid use-case to get access to devices, e.g., GPUs, as non-root user.

@AkihiroSuda
Copy link
Member

I understand the UID/GID for permissions but it's not clear why the eBPF device controller cannot be supported (is it more than capabilities, e.g. CAP_BPF?)

Yes, restricting devices require CAP_BPF.

Anyway, GPUs could be supported as long as the GPU device is chowned/chmodded

@AkihiroSuda AkihiroSuda added the question Further information is requested label Sep 8, 2021
@mythi
Copy link
Author

mythi commented Sep 8, 2021

@AkihiroSuda thanks for the prompt reply

Yes, restricting devices require CAP_BPF.

Is it possible to get rootless runc working with this?

Anyway, GPUs could be supported as long as the GPU device is chowned/chmodded

is it enough that the "rootless UID" belongs to that device group or the container process needs to have it part of the additionalGids too?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants