I have one of those mini fanless mini PC boxes with Proxmox and pfsense installed. Jellyfin has been installed as a lxc via one of the helper scripts. Set it up and it works fine.

I'm now trying to set it up to access an old Netgear ReadyNAS NV+ that I have lying around. It's been setup with SMB/CIFS as well as FTP access. I'm considering disabling SMB/CIFS access since I think I don't need that anymore. I think the NAS only supports TLS 1.2 protocol and it's probably safer to disable it security wise. After searching around, I've come across curlftpfs which seems to be able to mount a ftp server as a local directly which i can then use as a library for jellyfin.

Is this the best way or is there a better alternative I can consider?

Thanks.

you are viewing a single comment's thread
view the rest of the comments

[–] beerclue@lemmy.world 6 points 8 months ago (2 children)

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

[–] sramder@lemmy.world 3 points 8 months ago

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

[–] root@aussie.zone 1 points 6 months ago (1 children)

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@lemmy.world 1 points 6 months ago (1 children)

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@aussie.zone 1 points 6 months ago (1 children)

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@lemmy.world 1 points 6 months ago (1 children)

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@aussie.zone 1 points 6 months ago (1 children)

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

Many thanks. You've been very helpful.

[–] beerclue@lemmy.world 1 points 6 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.