• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting SOLVED: Can't get hardware transcoding to work

     
    • 0 Vote(s) - 0 Average

    SOLVED: Can't get hardware transcoding to work

    Fardenco
    Offline

    Junior Member

    Posts: 2
    Threads: 1
    Joined: 2025 May
    Reputation: 0
    Country:France
    #1
    2025-05-14, 11:54 PM (This post was last modified: 2025-05-15, 10:39 AM by Fardenco. Edited 1 time in total.)
    Hi,
    I'm trying to get hardware transcoding to work on my server but I don't know why it won't work.
    My Jellyfin server is running in a docker container.
    Jellyfin Server version is 10.10.7
    The CPU is an Intel Pentium Gold 8505
    I added the user to the "render" group, and added the group number and render devices in my docker.compose, following the documentation.
    But I have a feeling that the issue is still related to user group or at least to user.
    I'm using Portainer. If I open a container console with user "root", running the "/usr/lib/jellyfin-ffmpeg/vainfo" command, returns a list of profile.
    But if I do the same thing whith a console with user "1000", then the command returns an error.
    Because of this, I guess that the issue is not with the transcoding settings but maybe with the container settings ?

    When trying to play a movie with transcoding, the error shown in the logs is
    Code:
    Failed to set value 'vaapi=va:,vendor_id=0x8086,driver=iHD' for option 'init_hw_device': Generic error in an external library
    Error parsing global options: Generic error in an external library


    Here is my docker.compose :
    Code:
    services:
      jellyfin:
        image: jellyfin/jellyfin:latest
        container_name: Jellyfin-HT
        user: 1000:10
        group_add:
          - '105'
        environment:
          TZ: Europe/Paris
        volumes:
          - /volume1/docker/jellyfinht/config:/config:rw
          - /volume1/docker/jellyfinht/cache:/cache:rw
          - /volume1/docker/jellyfinht/logs:/logs:rw
          - type: bind
            source: /volume1/Jellyfin/Films
            target: /movies
          - type: bind
            source: /volume1/Jellyfin/Séries
            target: /tvshows
          - type: bind
            source: /volume1/Jellyfin/Musique
            target: /music
        devices:
          - /dev/dri/renderD128:/dev/dri/renderD128
          - /dev/dri/card0:/dev/dri/card0
        restart: on-failure:5
        network_mode: host

    Thank you for your help
    Go to solution
    bitmap
    Offline

    Community Moderator

    Posts: 776
    Threads: 9
    Joined: 2023 Jul
    Reputation: 24
    #2
    2025-05-15, 09:26 AM
    Double check you followed the steps in the HWA guide. There's more than just passing the device into the docker container.

    https://jellyfin.org/docs/general/post-i...tion/intel

    The verification steps can help you identify any issues. It might be a driver problem based on that error message.
    Jellyfin 10.10.7 LSIO Docker | Ubuntu 24.04 LTS | i7-13700K | Arc A380 6 GB | 64 GB RAM | 79 TB Storage

    [Image: AIL4fc84QG6uSnTDEZiCCtosg7uAA8x9j1myFaFs...qL0Q=w2400]
    Fardenco
    Offline

    Junior Member

    Posts: 2
    Threads: 1
    Joined: 2025 May
    Reputation: 0
    Country:France
    #3
    2025-05-15, 10:39 AM
    I believe I followed all the steps for Intel GPU on Linux with virtualization
    I found what the issue was
    My changes to the docker compose file were not used, because I was recreating the container from Portainer without previously updating the stack, it seems that the changes to the compose file are only taken into account after updating the stack.
    Because of that, the "add_group" option in my compose file was not used, I saw this when I used the "id" command in the container console and the render group was not present.
    Everything is working great now, thank you for your help
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode