![]() |
SOLVED: HW Transcoding issues and issue mapping /dev/dri to container - 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: SOLVED: HW Transcoding issues and issue mapping /dev/dri to container (/t-solved-hw-transcoding-issues-and-issue-mapping-dev-dri-to-container) |
HW Transcoding issues and issue mapping /dev/dri to container - TheChow - 2025-09-29 Edit: I forgot to mention I had Docker Desktop installed, and after some searching various places I found someone who had similar issues to mine and a reply saying they thought Docker Desktop may be an issue as they were unsure if it passes through devices. So I stripped Docker Desktop from my system and it works fine even without "privileged:true", but I need the user mapping. I'm running KDE Neon 6.4.5 (Ubuntu 24.04LTS) on a AMD Ryzen 9 7940HS (Radeon 780M graphics) laptop. The system is up to date from apt-get and Discover. I'm running into issues mapping /dev/dri to the Jellyfin container and have hit a wall in troubleshooting. I'm using the LinuxServer.io latest Jellyfin image. Here's a trimmed version of my Docker compose.yaml Code: services: If I don't have "privledge: true" I get an error "Error response from daemon: error gathering device information while adding custom device "/dev/dri": no such file or directory" With privledge it launches with "docker compose up", but if I open a shell on the container I don't see /dev/dri; and attempting to use VAAPI HW transcoding fails. I've tried with and without my ID specified, both result in missing /dev/dri inside the container. If I run "sudo docker compose up", and in the container I can see /dev/dri, and using the same settings in Jellyfin transcoding is successful. |