2023-10-19, 03:08 PM
Compose V3 doesn't support group_add. It doesn't work how people expect it to anyway. Everybody wants to use it to add the group ID of video/render outside the container. This might work, but not always. That flag adds the user inside the container to a group inside the container, so IDs need to be verified within the container for groups or semantic group names should be used. Just to reiterate, group_add won't work if you're specifying Compose V3.
Make sure your host user is the ID you expect and that it has been added to BOTH the video and render groups. If you don't see video and render (should be correct for Debian I think?) listed in the groups list for the host user, add them with...
This requires sudo privileges. I might also specify exactly which device you're using in as I've had issues using the generic /dev/dri path (iGPU will be /dev/dri/renderD128 and /dev/dri/card0). You can add both in your devices block by specifying the same designation on both sides of a colon; essentially copy what you have and add the specific devices.
Make sure your host user is the ID you expect and that it has been added to BOTH the video and render groups. If you don't see video and render (should be correct for Debian I think?) listed in the groups list for the host user, add them with...
Code:
usermod -aG <group_id or name>
This requires sudo privileges. I might also specify exactly which device you're using in as I've had issues using the generic /dev/dri path (iGPU will be /dev/dri/renderD128 and /dev/dri/card0). You can add both in your devices block by specifying the same designation on both sides of a colon; essentially copy what you have and add the specific devices.
Jellyfin 10.10.5 LSIO Docker | Ubuntu 24.04 LTS | i7-13700K | Arc A380 6 GB | 64 GB RAM | 79 TB Storage