Selfhosted

56476 readers

736 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

[Ubuntu] [Docker] Need help with Nvidia hardware acceleration in Jellyfin (sh.itjust.works)

submitted 23 hours ago* (last edited 23 hours ago) by LazerDickMcCheese@sh.itjust.works to c/selfhosted@lemmy.world

12 comments fedilink hide all child comments

Does anyone have a compose.yaml for an Nvidia GPU that works that they would like to share? Here's my current file, it gives a white screen with "server error" on it: https://pastebin.com/AaV17cTz

I went through Jellyfin's instructions on setting a GPU up, but the instructions weren't clear (in my opinion) so who knows if it's correct. I installed some Nvidia tools as a prerequisite and 'nvidia-smi' shows the card. I attached my Jellyfin settings from before it self-destructed according to Nvidia's transcoding matrix (which also wasn't descriptive enough in my opinion), do they look right for a 2080?

Update: after making this post, and changing nothing, it suddenly works

you are viewing a single comment's thread
view the rest of the comments

[–] jia_tan@lemmy.blahaj.zone 4 points 23 hours ago (4 children)

I have an intel igpu. It was hella painful to pass through the guy into a normal container and I never figured it out. I just ended up running the container with the —privileged flag. QuickSync hwaccel works fine now, I assume it would be the same for NVENC, since the flag basically just passes everything to the container.

[–] ohshit604@sh.itjust.works 1 points 3 hours ago* (last edited 3 hours ago)

Jellyfin isn’t the most secure piece of software out there, I would avoid giving it permissions it doesn’t need.

Step 1) Check /dev/dri for the GPU

user@debian:~/compose$ ls /dev/dri
total 0
drwxr-xr-x  3 root root        120 Jan 25 11:50 .
drwxr-xr-x 18 root root       3360 Feb 11 03:03 ..
drwxr-xr-x  2 root root        100 Jan 25 11:50 by-path
crw-rw----  1 root video  226,   0 Jan 25 11:50 card0
crw-rw----  1 root video  226,   1 Jan 25 16:39 card1
crw-rw----  1 root render 226, 128 Jan 25 11:50 renderD128

Documentation indicates renderDXXX typically refers to Intel GPU’s

Make sure at least one renderD* device exists in /dev/dri. Otherwise upgrade your kernel or enable the iGPU in the BIOS.

Edit your docker-compose.yaml and add this In your Jellyfin block

devices:
 - /dev/dri/renderD128:/dev/dri/renderD128

Start your container and enter it to verify the device is recognized.

sudo docker compose up -d; sudo docker exec -it jellyfin bash

Once inside ls /dev/dri to confirm the GPU is recognized inside the container, once you confirm it then you can exit the container.

user@debian:~/compose$ sudo docker exec -it jellyfin bash
I have no name!@jellyfin:/$ ls /dev/dri
renderD128
I have no name!@jellyfin:/$ exit
exit
user@debian:~/compose$

On the Jellyfin dashboard go to the hardware acceleration page and follow the notes left by Jellyfin devs.

[–] Lemmchen@feddit.org 1 points 11 hours ago* (last edited 11 hours ago)

Huh? I have an ARC A380 and I just followed the tutorial. AFAICT everything's working fine.

https://jellyfin.org/docs/general/post-install/transcoding/hardware-acceleration/intel#configure-with-linux-virtualization

[–] DonutsRMeh@lemmy.world 1 points 21 hours ago

Man, I have an intel iGPU myself, in a little Dell optiplex 7090 and it was a breeze on my Debian sever. Installed through apt and it’s running as a systemd service. No issues so far. Only one issue I had was when I played a 70GB 4k HDR movie that’s loaded with audio and subs and picture enhancements on my OLED TV. The server’s little fan was screaming and the movie kept pausing every 20 seconds. Other than that I have a ton of other movies and shows and I have no issues.

[–] Ebby@lemmy.ssba.com 1 points 22 hours ago

I use Intel too and had a heck of a time getting things working with portainer. Turns out portainer only worked with Nvidia (at least the version I used when I set it up). If I spun up the container via terminal, it worked.

I think a newer version may have added compatibility because I don't remember jumping through hoops with Immich.