• 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 Jellyfin Docker Permissions

    Pages (2): « Previous 1 2

     
    • 0 Vote(s) - 0 Average

    Jellyfin Docker Permissions

    Jellyfin Permission problems while setting up Gpu acceleration
    mark.monteiro
    Offline

    Team Member

    Posts: 1
    Threads: 0
    Joined: 2023 Jun
    Reputation: 0
    #11
    2023-10-01, 01:30 AM
    I just finished setting up GPU acceleration today and ran into the exact same issue you've described here. In the end I just skipped over the ldconfig step and everything seemed to work fine without it.

    I don't really know much about how the hardware acceleration stuff works, but if you've been having trouble getting it working, perhaps it's possible that the ldconfig issue is unrelated? In my case it took me a while to realize you need to run nvidia-smi on the host in order to verify that hardware acceleration is working. Running nvidia-smi from inside the container does not show any processes even when transcoding is happening.
    bitmap
    Offline

    Community Moderator

    Posts: 851
    Threads: 9
    Joined: 2023 Jul
    Reputation: 28
    #12
    2023-10-01, 09:00 AM
    Quote:Also I think by not using a uid:guid option I am using a privileged user(root) as the jellyfin documentation says.

    Misconception of what the documentation is trying to say. Setting the G/UID means the container interacts with files on your system as that user. It doesn't have all the same permissions as that user, but it acts as that user but proxy. So if you leave out the G/UID your volumes will appear to be owned by root/root which is not what you want (should be a service user or a well-secured non-root user).

    Setting the container as privileged essentially removes the walls around the container and allows it to interact with the rest of the system. It's dangerous to run a container as privileged all the time (big generalization) but necessary or easier in some cases. Privileged flag very different from setting G/UID. One is like NFS squash, the other is the keys to the host OS, kernel, and hardware.
    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]
    rsmartapps
    Offline

    Junior Member

    Posts: 5
    Threads: 1
    Joined: 2024 Jul
    Reputation: 0
    Country:Spain
    #13
    2024-08-01, 10:08 PM (This post was last modified: 2024-08-01, 10:09 PM by rsmartapps.)
    The issue is that your user doesn't have the mounted device drivers group, I managed to run the jellyfin container with the host user::group adding the required extra groups to the user.

    Code:
    services:
      jellyfin:
        image: jellyfin/jellyfin
        container_name: jellyfin
        user: "1000:1000"
        group_add:
        - 44  # GID for the video group
        - 992 # GID for the render group
        devices:
        - /dev/dri:/dev/dri
    Pages (2): « Previous 1 2

    « 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