Comments

• robber@lemmy.ml ⁨2⁩ ⁨hours⁩ ago

  As an alternative to mounting full /dev/dri, there are symlinks under /dev/dri/by-path/ which you can use. IIUC they are linked by the used PCI slot, hence should be as stable as the physical order of the cards.

  I use this pattern in a compose file:

  ...
  devices:
    - source: /dev/dri/by-path/pci-XXX-render
      target: /dev/dri/renderD128
      permissions: rwm
  

  source
• hperrin@lemmy.ca ⁨14⁩ ⁨hours⁩ ago

  Just mount /dev/dri.

  source

  • uuj8za@piefed.social ⁨4⁩ ⁨hours⁩ ago

    Genius!

    source

    • hperrin@lemmy.ca ⁨3⁩ ⁨hours⁩ ago

      I had the same issue a while ago. :) I think the docs tell you to do it the way you had it, which is why it causes confusion.

      source
  • yaroto98@lemmy.world ⁨5⁩ ⁨hours⁩ ago

    This is also good because if you have a newer cpu it has integrated graphics built in, and you have a dedicated gpu card, will give you two devices here, which this will auto mount both.

    source
• Appoxo@lemmy.dbzer0.com ⁨8⁩ ⁨hours⁩ ago

    jellyfin:
      container_name: jellyfin
      image: linuxserver/jellyfin:amd64-version-12.1ubu2604
      expose:
        - 8096
      networks:
        - media
      volumes:
        - ${DIR_LOCALTIME}:/etc/localtime:ro
        - ${DIR_container}/jellyfin/config:/config
        - ${DIR_media}/data:/media/data
      devices:
        # IntelQuickSync für TigerLake GT2 [Iris Xe Graphics]
        - /dev/dri/renderD128:/dev/dri/renderD128
        - /dev/dri/card0:/dev/dri/card0
      environment:
        PUID: 1200
        PGID: 1300
        #UMASK: 022
        TZ: ${TZ}
        DOCKER_MODS: linuxserver/mods:jellyfin-opencl-intel
        JELLYFIN_PublishedServerUrl: "https://jellyfin/.${DOMAIN_EXTERNAL}"
      deploy:
        resources:
          limits:
            memory: 10G
      group_add:
        - '44'
        - '992'
      labels:
        # Traefik:
        traefik.enable: true # Enable Traefik reverse proxy for the Traefik dashboard.
        traefik.http.services.jellyfin.loadbalancer.server.port: 8096
        traefik.http.routers.jellyfin-public.entrypoints: 'https'
        traefik.http.routers.jellyfin-public.rule: 'Host(`jellyfin.${DOMAIN_EXTERNAL}`)'
        # Secondary domain
        traefik.http.routers.jellyfin-public2.entrypoints: 'https'
        traefik.http.routers.jellyfin-public2.rule: 'Host(`jellyfin.${DOMAIN_EXTERNAL2}`)'
      restart: unless-stopped
  

  Afaik the card0 is only used for rendering to a desktop/monitor and for this purpose you should actually use the renderD128 path.
  But not sure either about this stuff. Sort of works for me. At least intel_gpu_top shows activity when transcoding :p

  source
• miaowoo_lw@lemmy.world ⁨13⁩ ⁨hours⁩ ago

  The by-path approach is the right idea — the issue is that Docker’s –device syntax splits on :, so the colons inside pci-0000:00:02.0-card confuse the parser (container_path gets mangled). Two things to try:

  1. Re-check the exact by-path filenames. They must match what’s actually in /dev/dri/by-path/ on your host — e.g. on Intel iGPU it’s usually pci-0000:00:02.0-card and pci-0000:00:02.0-render, but on some boards the PCI address differs. Run ls -l /dev/dri/by-path/ and confirm the symlink targets exist.

  2. Drop card entirely — you likely only need the render node. Modern VAAPI/QSV transcoding in Jellyfin works fine with just the render device, no card0 needed:

  devices:
    - /dev/dri/by-path/pci-0000:00:02.0-render:/dev/dri/renderD128
  

  This is also the most robust fix for your reboot problem: the render node via by-path doesn’t shuffle between reboots, so your compose file stops breaking.

  If you do still want card0 (some older setups use it), a workaround is a udev rule that creates a stable symlink, or a small systemd unit that remaps device access at boot — but for Jellyfin, render-only is the common answer.

  source