[Feature Request] Adding user to device group by default

[Dvalin21]

I spent the last few hours trying to figure out what was the issue of why my containers couldn't see my gpu.....turns out Frigate NVR could see and is using, but Jellyfin wasn't. Simple fix that apparently not in the documentation, add the current user of the host to the same group that the device is in aka video = card0 and render = renderD128. Possibly during setup of CasaOS there should be an auto detect for GPU and adding making it completely exposed to docker.

[tigerinus]

@Dvalin21

CasaOS runs under root user by default, which should have permissions for everything. Are you referring to something else?

[Dvalin21]

No, and I figured or at least assumed it was root. Not sure why I had to switch it in order to get it to be visible. I entirely admit I could be wrong.

…

On Mon, Dec 26, 2022 at 7:54 PM Tiger Wang ***@***.***> wrote: @Dvalin21 <https://github.com/Dvalin21> CasaOS runs under root user by default, which should have permissions for everything. Are you referring to something else? — Reply to this email directly, view it on GitHub <#785 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABY7PVIICPMTEX6KM3XHKODWPJD4BANCNFSM6AAAAAATJP6J3I> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[tigerinus]

I still don't get the idea of what needs to be done. Can you be more explicit?

[mojothemonkey2]

correct me if I'm talking rubbish, but I think it's related to AMD gpus..

so to access Nvidia gpu inside containers, you would use --gpus and --runtime=nvidia.

but this does not work for AMD gpus.
instead for these, you need to add the container user (eg normally uid=1000) to the video/render groups on the host.
and pass --devices=/dev/dri/... for drivers here.
https://jellyfin.org/docs/general/administration/hardware-acceleration/#amd-amf

there is some discussion here about how docker cli should support AMD and other gpus: docker/cli#2063 (comment)
so even the docker community has not sorted this yet.

would be pretty cool if we could give support for various gpus "out of the box".
eg, following the suggestions on the docker cli post, we could:

• add casaos user to video/render groups during install (as per this ticket).
• find as many graphics drivers as we can, and for each, append to container run with --devices=/dev/.. .
• also run with --gpus all and --runtime=nvidia. (may not be needed if we pass the drivers already?).

this way users don't need to worry about the extra gpu settings even.
maybe just a toggle in container settings for them to select gpu on/off.

users would still need to install the correct gpu drivers themselves (as I don't think we should try and manage that).
and it may not be possible to support all apps simultaneously - eg jellyfin uses the closed-source AMD driver, whilst another app migth want the open-source one.

but this could all be a complete rabbit hole of hardware support.

[Dvalin21]

@tigerinus According to the AMD driver install instructions, even with root you need to add the current user of the host to the render and video group. This will allow for the drivers and device to be available to all containers. @mojothemonkey2 you are correct.