• 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 Updated container has gone all wrong

     
    • 0 Vote(s) - 0 Average

    Updated container has gone all wrong

    Femur4889
    Offline

    Junior Member

    Posts: 8
    Threads: 1
    Joined: 2024 May
    Reputation: 0
    Country:United States
    #6
    2024-05-08, 02:52 AM
    (2024-05-07, 11:58 PM)TheDreadPirate Wrote: I forgot about this.  You need to add "group_add" in your docker compose.  Mine for reference.

    Code:
    services:
      jellyfin:
        image: jellyfin/jellyfin:unstable
        container_name: jellyfin-unstable
        user: 105:104
        group_add:
          - "993" # Intel render group
        network_mode: 'host'
        volumes:
          - ./jellyfin-data/config:/config
          - ./jellyfin-data/cache:/cache
          - /media/storage2:/media/storage2:ro
          - /media/library:/media/library:ro
        devices:
          - /dev/dri/renderD128:/dev/dri/renderD128
        restart: 'unless-stopped'
        extra_hosts:
          - "host.docker.internal:host-gateway"

    Use the command "getent group render" and replace "993" in mine with your system's render group ID.




    Setting getent in the docker compose to my computer's value didn't change anything. I am still completely unable to load JF in the browser if I specify my user 1000:1000, and am still able to load JF if this is commented out.

    I have also tried to set up a completely fresh instance of JF Docker, using different /config /cache and /media locations, but nothing is working.

    I am truly and totally confused. Any other ideas? The only thing that has changed in my server over the past year is that I moved the media files from one ext4-formatted HD to a ZFS pool. Other than that, I am completely certain that my /config and /cache haven't changed at all.
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    Messages In This Thread
    Updated container has gone all wrong - by Femur4889 - 2024-05-07, 07:55 PM
    RE: Updated container has gone all wrong - by TheDreadPirate - 2024-05-07, 08:12 PM
    RE: Updated container has gone all wrong - by TheDreadPirate - 2024-05-07, 08:27 PM
    RE: Updated container has gone all wrong - by Femur4889 - 2024-05-07, 08:41 PM
    RE: Updated container has gone all wrong - by TheDreadPirate - 2024-05-07, 11:58 PM
    RE: Updated container has gone all wrong - by Femur4889 - 2024-05-08, 02:52 AM
    RE: Updated container has gone all wrong - by bitmap - 2024-05-08, 03:36 AM
    RE: Updated container has gone all wrong - by Femur4889 - 2024-05-08, 07:42 PM
    RE: Updated container has gone all wrong - by Femur4889 - 2024-05-08, 09:06 PM
    RE: Updated container has gone all wrong - by 3216 - 2024-05-08, 09:21 PM
    RE: Updated container has gone all wrong - by Femur4889 - 2024-05-08, 11:01 PM
    RE: Updated container has gone all wrong - by Femur4889 - 2024-05-08, 11:11 PM

    • 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