Jellyfin server in Portainer issues

[nextguy]

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:

  
version: "2.1"
services:

    jellyfin:
    image: jellyfin/jellyfin:latest
    container_name: jellyfin
    network_mode: host
    #environment:
    #  - PUID=I am not sure what to put here so it is commented out
    #  - PGID=I am not sure what to put here so it is commented out
    volumes:
      - /srv/dockerdata/jellyfin/config:/config
      - /srv/dockerdata/jellyfin/cache:/cache
      - /srv/Media:/media
    group_add:
      - "105"
    devices:
      - /dev/dri/:/dev/dri/
    restart: unless-stopped

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
crw-rw---- 1 root video  226,  0 Feb 23 09:16 card0
crw-rw---- 1 root render 226, 128 Feb 23 09:16 renderD128

And if I do a getent on "render" I get this:

Code:

getent group render | cut -d: -f3

105

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
crw-rw---- 1 root  105 226, 128 Feb 23 14:16 renderD128

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?

[TheDreadPirate]

That looks correct. "getent group render | cut -d: -f3" is the correct way to get the group ID for the render group.