Jellyfin: empty library

  • Post the YML inside a CODE box that you used to launch Jellyfin

  • Do you mean this?

  • Do you mean this?

    Does your PUID:PGID have R/W access to the folders you are using?


    Does the media PATH matches the HOST path where the files are?

  • I set up the container as the admin user, I also created two users:

    Code
    Name        UID    GID
    appuser     1000   100
    myname      1001   100

    Under Services -> Compose -> Files I then created a new File and filled it with the content above.


    Quote

    Does the media PATH matches the HOST path where the files are?

    I’m not sure what that means. I have a shared folder named “media” under /dev/media. I tried placing files directly inside the media folder as well as creating sub folders (phone and camera).

  • I have a shared folder named “media” under /dev/media

    /dev path is for devices and not a place to put files.

    You should use the /srv/dev-disk-by-uuid-xxxx-yyy-zzzz/media proper.


    Check and post

    lsblk

    blkid

  • /dev path is for devices and not a place to put files.

    You should use the /srv/dev-disk-by-uuid-xxxx-yyy-zzzz/media proper.

    Sorry, I this is what I meant. I am using /srv/dev-disk-by-uuid-xxxx-yyy-zzzz/media


    lsblk


    blkid

    Code
    /dev/mmcblk0p3: UUID="08862897-d128-463f-b19c-aa85f8cb4d68" TYPE="swap" PARTUUID="87eeab16-682f-4987-87a8-4b9fee0fb1b7"
    /dev/mmcblk0p1: UUID="53EB-4725" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="73ee23e7-9288-4953-8fc1-a47dabfa21fb"
    /dev/mmcblk0p2: UUID="7deea527-4c1b-4dd4-9b8f-54cc22250c08" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="1b7e6bf9-cd0e-4420-9e2d-ab2cbed
    0c032"
    /dev/sda1: UUID="ce014ef7-3318-4783-884c-3cc6c60a3d74" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="dd50e21d-0c21-4e22-9610-17f17e553ec5
    "
  • ls -al /srv/dev-disk-by-uuid-ce014ef7-3318-4783-884c-3cc6c60a3d74

  • ls -al /srv/dev-disk-by-uuid-ce014ef7-3318-4783-884c-3cc6c60a3d74

  • ls -al /srv/dev-disk-by-uuid-ce014ef7-3318-4783-884c-3cc6c60a3d74/media


    id appuser

    id myname

  • ls -al /srv/dev-disk-by-uuid-ce014ef7-3318-4783-884c-3cc6c60a3d74/media

    Code
    drwxrwsr-x+ 4 root users 4096 12. Apr 10:54 .
    drwxr-xr-x  8 root root  4096  9. Apr 22:25 ..
    drwxrwsr-x  3 myname  users 4096 10. Apr 18:20 Photo
    drwxr-xr-x  8 root root  4096  9. Apr 22:25 ..
    drwxrwsr-x  3 myname  users 4096 10. Apr 18:20 Photo
    drwxrwsr-x  3 myname  users 4096 10. Apr 21:20 Video


    id appuser

    Code
    uid=1000(appuser) gid=100(users) Gruppen=100(users)


    id myname

    Code
    uid=1001(myname) gid=100(users) Gruppen=100(users)

    Thanks for your help and your patience btw!

  • drwxrwsr-x 3 myname users 4096 10. Apr 21:20 Video

    Is there a awkward character on that folder?

    ls -al /srv/dev-disk-by-uuid-ce014ef7-3318-4783-884c-3cc6c60a3d74/media/Video



    Since I think it's more accurate to use full paths on the YMLs (I don't use the ENV box for nothing), you can use the YML like this to be sure that all PATHs go on the correct folders and with the correct permissions.


    Bring down the container and edit the file with this CODE (delete what you have and copy/paste this)

    Don't forget to edit the needed remarks:

  • Is there a awkward character on that folder?

    ls -al /srv/dev-disk-by-uuid-ce014ef7-3318-4783-884c-3cc6c60a3d74/media/Video

    Yes, there was a space at the end! I totally missed that…


    I copied the code to the YML file (edited the necessary changes). After getting the container up again a second folder “Video” appeared. I renamed the old folder so that there’s no longer a space at the end and deleted the new folder (I couldn’t put files inside the new folder, permission denied). Unfortunately, the library still appears empty.


    Maybe I’d better start all over again…


    Success! I changed line 13:

    Code
    - /srv/dev-disk-by-uuid-ce014ef7-3318-4783-884c-3cc6c60a3d74/media/Video:/data/Video/


  • This is might be part of your problem:


    ls -al /srv/dev-disk-by-uuid-ce014ef7-3318-4783-884c-3cc6c60a3d74


    drwxrwsr-x+ 4 root users 4096 12. Apr 10:54 media


    Only root and others can enter the directory.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.


  • It is working now! I’ve edited my post above.

    Do you think I still need to change something here?

  • It is working now! I’ve edited my post above.

    Do you think I still need to change something here?

    Well, it's a matter of style so some things are up to you to decide. But a thorough understanding of filesystem ownerships and permissions is a needed in general, and especially with Docker.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

  • But a thorough understanding of filesystem ownerships and permissions is a needed in general, and especially with Docker.

    Yes, I see that now. I’ve installed Jellyfin directly (without Docker) before, permissions were a bit more accessible to me. At the moment I’m just happy that everything works.


    Thank you again, Soma :)

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!