Jellyfin access to nfs media folder on NAS #2038
Replies: 2 comments 6 replies
-
Is this an unpriviledged container or a priviledged one? In case you want to switch this container to priviledged you can either redeploy or backup and re-import it as privil.. , but its just a rather unedacutated guess from myself , i get with the three keywords "user rights, container, UI stopped working"... |
Beta Was this translation helpful? Give feedback.
-
this is very easy to do
you cannot map the root folder in a NAS so you may want to map a folder like for example "music"
mkdir -p /mnt/nasmedia
pct set 100(whatever your container id is) -mp0 /mnt/pve/music,mp=/mnt/nasmedia thats it. not reboot the container and you will be able to see the folder inside the container |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi
I've recently moved from a docker instance of Jellyfin to an LXC in Proxmox using the vrey helpful scripts here (thanks!). I cannot seem to get Jellyfin to access my shared media folder on my NAS which is mapped to the LXC as an NFS folder:
mp0: /mnt/pve/movies,mp=/mnt/movies
My movies folder has the following owner setup, as shown from within the jellyfin lxc:
root@jellyfin:/mnt/movies# ls -al
total 20947512
drwxrwxrwx 11 100000 100000 4096 Nov 12 07:52 .
drwxr-xr-x 3 root root 4096 May 4 2023 ..
drwxrwxrwx 2 100000 100000 4096 Oct 19 2022 .@__thumb
drwxrwxrwx 2 100000 100000 4096 Aug 13 22:21 'movie1
drwxrwxrwx 2 100000 100000 4096 Aug 12 00:53 'movie2'
drwxrwxrwx 2 100000 100000 4096 Aug 12 01:34 'movie3'
This setup works with the arr apps when I complete idmapping in the lxc config as per:
lxc.idmap: u 0 100000 1000
lxc.idmap: g 0 100000 1000
lxc.idmap: u 1000 1000 1
lxc.idmap: g 1000 1000 1
lxc.idmap: u 1001 101000 64535
lxc.idmap: g 1001 101000 64535
However this doesn't work in the jellyfin lxc - there are permissions issues. Digging into this, jellyfin runs as user 110 in group 118 in the lxc:
root@jellyfin:/var/log/jellyfin# less /etc/passwd | grep jellyfin
jellyfin:x:110:118:Jellyfin default user,,,:/var/lib/jellyfin:/bin/false
So I tried mapping 110 to 100000 and root to root:
lxc.idmap: u 0 0 110
lxc.idmap: g 0 0 118
lxc.idmap: u 110 100000 1
lxc.idmap: g 118 100000 1
lxc.idmap: u 111 111 889
lxc.idmap: g 119 119 881
lxc.idmap: u 1000 1000 1
lxc.idmap: g 1000 1000 1
lxc.idmap: u 1001 101000 64535
lxc.idmap: g 1001 101000 64535
which seems to give jellyfin access to the files:
root@jellyfin:/mnt/movies# ls -al
total 20947512
drwxrwxrwx 11 jellyfin jellyfin 4096 Nov 12 07:52 .
drwxr-xr-x 3 root root 4096 May 4 2023 ..
drwxrwxrwx 2 jellyfin jellyfin 4096 Oct 19 2022 .@__thumb
drwxrwxrwx 2 jellyfin jellyfin 4096 Aug 13 22:21 'movie1'
drwxrwxrwx 2 jellyfin jellyfin 4096 Aug 12 00:53 'movie2'
However the jellyfin UI now has stopped working and gives and unable to connect message. I also get permissions errors viewing the error log in /var/logs/jellyfin.
I've seen similar discussions so hoping someone has cracked this issue or has an alternative approach. I cannot see anything relating to giving the jellyfin user the necessary permissions outside the lxc though. Ideally I wouldn't have to rework permissions for all my arr apps and can make Jellyfin work with this existing setup. Any thoughts welcome. I'm not that familiar with idmapping so its entirely possible I haven't got that quite right.
Beta Was this translation helpful? Give feedback.
All reactions