![]() |
Jellyfin server in Portainer issues - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +--- Thread: Jellyfin server in Portainer issues (/t-jellyfin-server-in-portainer-issues) |
Jellyfin server in Portainer issues - nextguy - 2024-02-23 I have a Dell Optiplex 7010 Plus on which I've installed Proxmox. And I have setup the Proxmox to passthrough the iGPU (detected as UHD Graphics 770) as per numerous articles. Currently I have a single Debian guest wtih Docker and Portainer in which I've installed Jellyfin. My Debian install is very basic and I'm not sure if I've set everything up correctly. The Portainer setup for Jellyfin is as follows: Code: With regards to the group_add "105", I put 105 because when I run "cd /dev/dri && ls -l" on the Debian guest I get this: Code: drwxr-xr-x 2 root root 80 Feb 23 09:16 by-path And if I do a getent on "render" I get this: Code: getent group render | cut -d: -f3 But I was curious about what actually happens in the container. So I ran this command to get a shell into the container: Code: docker exec -it jellyfin sh And if I run "cd /dev/dri && ls -l" in that shell I get this: Code: crw-rw---- 1 root video 226, 0 Feb 23 14:16 card0 As you can see, there is no group called render. Instead it is called 105. So anyways I'm really confused about this. Did I miss something? RE: Jellyfin server in Portainer issues - TheDreadPirate - 2024-02-23 That looks correct. "getent group render | cut -d: -f3" is the correct way to get the group ID for the render group. |