Selfhosted

41084 readers

265 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.

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

[email protected]

Cannot get jellyfin docker container to use nvenc hardware acceleration (lemmy.ml)

submitted 1 day ago* (last edited 1 day ago) by [email protected] to c/[email protected]

11 comments fedilink hide all child comments

cross-posted from: https://lemmy.ml/post/24722787

I am running ubuntu with casa os. I was previously running an intel apu (the name has slipped me I will update the post when I can with this info). Recently I got a 1650 that I installed for nvenc transcoding. It seems all the proper drivers are installed but my jellyfin container still fails playback anytime with it turned on.

I have reinstalled the container with the nvidia device variable and no dice. I have also tried installing the nvidia cintainer toolkit but that didn't work either. I am at a loss for trying to get nvenc to work.

Any help is appreciated!

EDIT: here is the ffmpeg log file

https://gofile.io/d/9nsBFq

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

[–] [email protected] 1 points 1 day ago (1 children)

You need to be running the Nvidia container toolkit and specify the container be launched with that runtime if you want direct hardware access to enc/dec hardware.

[–] [email protected] 1 points 1 day ago (3 children)

I followed this guide and seemed to get it working.

https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html

However jellyfin transcoding sttill doesn't work. I have tried adding the "nvidia devices= all" environment variable, it still didn't work.

I tried using the docker conpose from here

https://jellyfin.org/docs/general/administration/hardware-acceleration/nvidia/#configure-with-linux-virtualization

But when I try and run this command: "docker exec -it jellyfin ldconfig sudo systemctl restart docker"

It says the container is restarting and to try again when the container has started.

[–] [email protected] 2 points 1 day ago (1 children)

I had the same issue a few weeks ago. Try this in your docker compose

deploy:
      resources:
        reservations:
          devices:
            - driver: cdi
              device_ids:
                - nvidia.com/gpu=all

[–] [email protected] 1 points 1 day ago* (last edited 1 day ago)

This is what thay compose looks like now:

 services:
  jellyfin:
    image: jellyfin/jellyfin
    user: 1000:1000
    network_mode: 'host'
    volumes:
      - /DATA/AppData/jellyfin/config:/config
      - /DATA/AppData/jellyfin/cache:/cache
      - /DATA/AppData/jellyfin/media:/media
      - /mnt/drive1/media:/mnt/drive1/media
      - /mnt/drive2/Jellyfin:/mnt/drive2/Jellyfin
      - /mnt/drive3:/mnt/drive3
      - /mnt/drive4/media:/mnt/drive4/media
      - /mnt/drive5/jellyfin:/mnt/drive5/jellyfin
      - /mnt/drive6/jellyfin:/mnt/drive6/jellyfin
    runtime: nvidia
    deploy:
      resources:
        reservations:
          devices:
            - driver: cdi
              device_ids:
               - nvidia.com/gpu=all
            - /dev/nvidia-caps:/dev/nvidia-caps
            - /dev/nvidia0:/dev/nvidia0
            - /dev/nvidiactl:/dev/nvidiactl
            - /dev/nvidia-modeset:/dev/nvidia-modeset
            - /dev/nvidia-uvm:/dev/nvidia-uvm
            - /dev/nvidia-uvm-tools:/dev/nvidia-uvm-tools
              count: all
              capabilities: [gpu]

Edit: when I try and compose up it says "yaml: lin 30 mapping values are not allowed in this context" when I remove line 30 and 31 the output is "validating /DATA/AppData/jellyfin/docker-compose.yml: services.jellyfin.deploy.resources.reservations.devices.1 must be a mapping"

[–] [email protected] 2 points 1 day ago (1 children)

I have no guidance on your issue but just to make sure, this is two commands and not one:

docker exec -it jellyfin ldconfig

sudo systemctl restart docker

Do you get the restarting message with just the first command?

[–] [email protected] 1 points 1 day ago

I ran it as two commands instead of one before and still got that error message.

However, I tried again with a different jellyfin image and the command seems to have ran fine.

[–] [email protected] 0 points 1 day ago (1 children)

'docker exec -it jellyfin nvidia-smi'

[–] [email protected] 1 points 1 day ago* (last edited 1 day ago) (1 children)

I tried this and it says:

OCI runtime exec failed: unable to start container process: exec: "nvidia-smi": executable file not found im $PATH: unknown

[–] [email protected] 1 points 1 day ago

Sure seems like you're either sourcing these images wrong, or they're missing something. The docs themselves even reference this command as it's a good way to test the container is linked to the host hardware properly.

Maybe try starting a shell and finding if that executable exists in the image.