• 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: Jellyfin Requires chmod -R 777 Periodically for Hardware Transcoding

     
    • 0 Vote(s) - 0 Average

    SOLVED: Jellyfin Requires chmod -R 777 Periodically for Hardware Transcoding

    [Ubuntu Docker] Jellyfin Requires chmod -R 777 /dev/dri Periodically for Hardware Transcoding
    Kein
    Offline

    Junior Member

    Posts: 9
    Threads: 3
    Joined: 2023 Nov
    Reputation: 0
    Country:Romania
    #1
    2025-01-12, 07:37 AM
    Hi,

    I’m encountering a recurring issue with my Jellyfin setup where hardware transcoding stops working unless I manually adjust permissions for /dev/dri. Here are the details of my setup and problem:

    System Details:

    Jellyfin Version: 10.8.10

    Platform: Ubuntu 24.04.1 LTS

    Installation Method: Docker

    Hardware:

    CPU: Intel Core i5-7500 (with integrated Intel HD Graphics 630)

    GPU: Using /dev/dri for Intel iGPU hardware acceleration



    Issue Description:
    Hardware transcoding works correctly after a fresh setup. However, periodically transcoding fails, and I need to run the following commands to restore functionality:

    sudo chmod -R 777 /dev/dri 
    docker restart jellyfin

    I expect Jellyfin to consistently access /dev/dri for hardware transcoding without requiring manual intervention.

    Steps Taken:

    1. Mounted /dev/dri in the container using:

    --device /dev/driConfused-facedev/dri


    2. Set permissions 660 for /dev/dri to see if there's any difference:

    sudo chmod -R 660 /dev/dri 
    sudo chown -R root:video /dev/dri


    3. Added the Docker user to video and render groups:

    sudo usermod -aG video,render $(whoami)



    Despite these efforts, the issue reappears after some time. I’m unsure if this is due to Docker, system permissions resetting, or Jellyfin’s handling of /dev/dri.

    Logs:
    I’ve attached debug-level logs showing what happens when transcoding fails (available upon request).

    What I Need Help With:

    How can I ensure persistent access to /dev/dri for Jellyfin without needing to run chmod and restart the container?

    Is there a better way to configure permissions or system settings to fix this issue?


    Thank you in advance for your help!



    Does this adhere to the guidelines and clearly explain the problem?


    Attached Files
    .txt   _jellyfin_logs.txt (Size: 18.06 KB / Downloads: 42)
    Go to solution
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2025-01-12, 04:11 PM
    You need to pass in the render group into the container.

    Code:
    group_add:
          - '993' # Intel render group
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    « 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