Using curlftpfs with jellyfin to access media stored on old NAS?

root OP , 2 months ago

I finally got around to getting things set up, and for some reason, the container I created for jellyfin refused to allow NFS mounting.

I ended up trying a "Turnkey Media Server" template which ended up working. It also didn't allow NFS mounts, but it did allow CIFS mounting, which I used. Jellyfin is now refreshing the library. So far so good.

entropicdrift , 3 months ago

CIFS is probably more robust than curlftpfs, but I'd probably just go full NFS on it if you care about performance.

root OP , 2 months ago

I ended up mounting the NAS share via CIFS and it appears to be working.

possiblylinux127 , 3 months ago

Maybe you could try swapping out the OS? What model is it? Its likely insecure due to a lack of updates anyway

sramder , 3 months ago

I’ve never even heard of curlftpfs, but I can’t think of a reason why it wouldn’t work. You should try it out and let us know… I tried NFS once and didn’t like it.

beerclue , 3 months ago

Why don't you try NFS? For me it's a lot easier to set up...

sramder , 3 months ago

Because insecure FTP access is already enabled on the NAS ;-)

root OP , 2 months ago

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.

beerclue , 2 months ago

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.

root OP , 2 months ago

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.

beerclue , 2 months ago

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...

root OP , 2 months ago

"noauto" sounds like a step in the right direction. I might give it a shot.

Many thanks. You've been very helpful.

beerclue , 2 months ago

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.