2025-05-05, 04:35 AM
Hello fellow fins of jelly!
I have previously had jellyfin running on ubuntu for a while with hardware transcoding working.
I have recently moved over to a docker container setup, this is mostly working except for hardware transcode.
I'm almost certainly missing something daft.
I have passed my /dev/dri path as a device.
If I docker bash into the container /dev/dri shows entries for a card1 & renderD128 device.
I've tried flip flopping between QSV/VAAPI and leaving blank the render device or explicitly naming /dev/dri/renderD128.
But my CPUs all hit the rafters when I transcode.
I'm not seeing much in the way of logs, perhaps I'm missing something but essentially the software transcode is working so I guess nothing much to report.
I'm not using compose, I run the following to create the container:
docker run -d \
--name jellyfin \
--user 1000:1000 \
--device /dev/dri \
--group-add video \
-v /my/config
config \
-v /my/media
media \
-p 8096:8096 \
jellyfin/jellyfin:latest
Any pointers appreciated!
I have previously had jellyfin running on ubuntu for a while with hardware transcoding working.
I have recently moved over to a docker container setup, this is mostly working except for hardware transcode.
I'm almost certainly missing something daft.
I have passed my /dev/dri path as a device.
If I docker bash into the container /dev/dri shows entries for a card1 & renderD128 device.
I've tried flip flopping between QSV/VAAPI and leaving blank the render device or explicitly naming /dev/dri/renderD128.
But my CPUs all hit the rafters when I transcode.
I'm not seeing much in the way of logs, perhaps I'm missing something but essentially the software transcode is working so I guess nothing much to report.
I'm not using compose, I run the following to create the container:
docker run -d \
--name jellyfin \
--user 1000:1000 \
--device /dev/dri \
--group-add video \
-v /my/config

-v /my/media

-p 8096:8096 \
jellyfin/jellyfin:latest
Any pointers appreciated!