Trixie - Jellyfin under Docker with Nvidia transcode?

  • Yes it's an intel i7 7700K

    Code
    nvidia-ctk cdi generate --output=/etc/cdi/nvidia.yaml


    Code
    docker run --rm --runtime=nvidia --gpus all ubuntu nvidia-smi
    Code
    docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: could not apply required modification to OCI specification: error modifying OCI spec: failed to inject CDI devices: unresolvable CDI devices runtime.nvidia.com/gpu=all
    
    Run 'docker run --help' for more information


    Code
    # devices:
    #      - /dev/dri:/dev/dri

    The same.

  • Already done twice during your guide and leave Docker storage blank

    sudo nvidia-ctk runtime configure --runtime=docker


    sudo systemctl restart docker

    I try

    Code
    apt install nvidia-kernel-dkms nvidia-driver
    Code
    nvidia-kernel-dkms is already the newest version (550.163.01-2).
    nvidia-kernel-dkms set to manually installed.
    nvidia-driver is already the newest version (550.163.01-2).

    :/

  • Hm, lets recap:


    Nvidia-driver installed successfully. Confirmed by nvidia-smi


    Docker installed successfully, confirmed by running nvidia-smi in a container (docker exec -it jellyfin nvidia-smi)


    nvidia container toolkit has an issue. (Runtime nvidia does not work in a docker container) CDI error 255 just states, that there was an error starting the container. May be you could find any logging information for your jellyfin container.


    So we have to focus on that.


    Please doublecheck Step 4 to Step 6, specially the compose-part with the config in OMV GUI


    One thing to try could be installing the experimental version of the toolkit. But first check the upper.

  • I doublecheck Step 4 to Step 6. Everything is OK


    my compose for jellyfin

    When I start the container, no error:

    https://drive.google.com/file/d/18w_uDp0r_2Hi00blGUGHIdHDExNyIn19/view?usp=drive_link


    And when I launch a movie with hw:

    https://drive.google.com/file/d/10MID9QS5NEF2wMzQjjiyJIcJPJ19U5sJ/view?usp=drive_link

    We can see the FFMpeg error.


    Trying to install the experimental packages

    Code
    sudo sed -i -e '/experimental/ s/^#//g' /etc/apt/sources.list.d/nvidia-container-toolkit.list

    then

    Code
    sudo apt-get update
    
    export NVIDIA_CONTAINER_TOOLKIT_VERSION=1.18.1-1  sudo apt-get install -y \      nvidia-container-toolkit=${NVIDIA_CONTAINER_TOOLKIT_VERSION} \      nvidia-container-toolkit-base=${NVIDIA_CONTAINER_TOOLKIT_VERSION} \      libnvidia-container-tools=${NVIDIA_CONTAINER_TOOLKIT_VERSION} \      libnvidia-container1=${NVIDIA_CONTAINER_TOOLKIT_VERSION}

    and

    Code
    sudo nvidia-ctk runtime configure --runtime=docker
    
    sudo systemctl restart docker

    The same

  • That's it!!


    We're here!! That's the trick!

    I forgot to apt upgrade 8o


    I can transcode without any error and nvidia-smi post jellyfin ffmpeg!


    THANK YOU VERY MUCH!!!!!! :love:

  • One more quick question to clarify things:


    I need to stay on the Linux kernel 6.12.57+deb13-amd64. I tried reverting to 6.17.13 to test, and I get an Docker OCI error when starting Jellyfin.


    So I reverted to 6.12, and everything is OK.


    I need to check, once the kernel is updated, that I'm still on 6.12 by default?

  • bugado

    Added the Label resolved
  • Yes you need to stick with 6.12. 6.14 might also work.


    I'm not sure if there is a Proxmox Kernel Version 6.17. If it is available you could try that one (OMV GUI - Kernel - Install Proxmox Kernel)

  • Okay, I gave it a try.

    I installed kernel 6.17.4 pve, upgrade, reboot but I'm still getting the same OCI error when starting the Jellyfin container.


    I'm going back to 6.12 non proxmox.


    Thanks again, and see you soon.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!