this post was submitted on 10 Mar 2024
1 points (100.0% liked)
Jellyfin: The Free Software Media System
5740 readers
11 users here now
Current stable release: 10.10.1
Matrix (General Information & Help)
Matrix (Off-Topic) - Come get to know the team and blow off steam!
Matrix Space - List of all the available rooms on Matrix.
Discord - Bridged to our Matrix rooms
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I tried to mount the share as NFS, but it didn't seem to work from the console in the container. I ended up using CIFS which worked.
Probably the container does not have the required NFS client/libraries, but you don't have to do this inside the container... You mount it on the host and share it via a docker volume with the container.
I have installed nfs-kernel-server packages. I think it is possibly a permissions issue.
I briefly considered mounting it on the host (Proxmox) layer, but the way I have things set up, I only power on the NAS if I need to access it. Most of the time the Proxmox hardware will be booting up when the NAS is off and I think it will cause boot issues trying to mount a NAS share which it cannot find.
Remember that the container sits on a different network, the docker network, maybe that's why access doesn't work.
You can add the mount to be
noauto
in fstab, so it doesn't mount it unless you access the location. You can also mount it manually or via script, as needed.Not sure how to help more, you have a peculiar setup...
"noauto" sounds like a step in the right direction. I might give it a shot.
Many thanks. You've been very helpful.