(2024-10-22, 09:40 PM)TheDreadPirate Wrote: Can you share your full docker compose for Jellyfin?  Also, since you mentioned PUID and PGID, I'm assuming you're using the linuxserver image for Jellyfin?

What file system is your hard drive using?  And since it is mounted in /media/[user]/[drive folder] I am assuming you allowed Linux to auto-mount this drive, correct?  Consider manually mounting it in a different location since /media/[user] is protected by an ACL that is likely the reason that Jellyfin is unable to access the contents.

I wrote up a guide for doing that at the link below.

https://forum.jellyfin.org/t-mounting-local-storage-in-linux-linux-permissions-primer

(2024-10-23, 02:19 AM)TheDreadPirate Wrote: Two things.  First, the folder you mounted it in is protected by an ACL, /media/[name].  You COULD remove the ACL, but you should move it out of /media/[name] since all removable media gets mounted there.  To remove the possibility of a naming collision or udisk2 (what mounts storage in that directory) could possibly re-apply the ACL.

So I strongly recommend moving your drive mount elsewhere.  Even /media is fine.  /media/big.

Second, you need to provide a container path for the volumes in your docker compose.

Code:

    volumes:
      - ./jellyfin_config:/config
      - /media/[name]/big/jellyfin/media/books
      - /media/[name]/big/jellyfin/media/movies
      - /media/[name]/big/jellyfin/media/music
      - /media/[name]/big/jellyfin/media/shows

Should be something like this, after you've changed where it is mounted.

Code:

    volumes:
      - ./jellyfin_config:/config
      - /media/big/jellyfin/media/books:/books
      - /media/big/jellyfin/media/movies:/movies
      - /media/big/jellyfin/media/music:/music
      - /media/big/jellyfin/media/shows:/shows

If you're still having issues, we can double check the permissions.  Remember, from my guide, the user that runs the container needs to have, at a minimum, r-x permissions to navigate the folder structure.  FOR EVERY FOLDER IN THE PATH.

A tip for Linux permissions.  Noobies make it out to be too complex.  It is really simple.  Ask yourself two questions: 1) What am I trying to do? 2) What are the permissions for my ownership level for my current location.

For 1, the three possible answers are read, write, and executing.  Some actions require more than one of these.  Like "cd", as I described in my guide, requires reading and executing permissions.

For 2, the three ownership levels are "user", "group", and "other".  Which are you in?  What are the permissions for that ownership level?  Does my ownership level have sufficient permissions for the desired action and/or target file/folder?

Also, since you are using the official jellyfin image, you don't use PUID and PGID.

Code:

services:
  jellyfin:
    image: jellyfin/jellyfin
    container_name: jellyfin
    user: 1000:1000  # you use this to have the container run as your user.
    environment:
      - TZ=Americas/New_York
    volumes:
      - ./jellyfin_config:/config
      - /media/big/jellyfin/media/books:/books
      - /media/big/jellyfin/media/movies:/movies
      - /media/big/jellyfin/media/music:/music
      - /media/big/jellyfin/media/shows:/shows
    ports:
      - "8096:8096"
    restart: 'unless-stopped'