11
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 10 Mar 2024
11 points (100.0% liked)
Jellyfin: The Free Software Media System
5605 readers
21 users here now
Current stable release: 10.10.2
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
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.
No worries, glad to be of help. I still think that you should do this on the host, not the container. Containers revert your manual changes on an update, they sit on a different network, it's a mess.
Just for reference, this is how I have my NAS mounts on my machine (
/etc/fstab
):10.10.10.14:/volume1/backup /home/beerclue/priv/nas/backup nfs noauto,user,rw,vers=4.0 0 0
And on the NAS I have it set like (
/etc/exports
):/volume1/backup 10.10.10.17(rw,async,no_wdelay,crossmnt,all_squash,insecure_locks,sec=sys,anonuid=1024,anongid=100)
I'm not saying this is the perfect setup, but it works for me. I see the mount in my file explorer, and it only mounts it when i click on it, or when I tell it to from the terminal, so no boot impact even if I am away.