I have Truenas Scale as a file repository. Then Proxmox on seperate machine but same network. On Proxmox I have VM withe several services. Some of these store several GBs of data so i would lime to mount datasets to Proxmox. What is the best wat of doing this? Mount a single nfs share to proxmox and the mount this share in the vm or should i mount the truenas daraset directly in the vm? The latter semms simpler? My.main cincern is avoiding disasters on services, vm and proxmox il nas goes offline for whatever reason. Is there a way to deal with this risk?
Mount it in the VM, not as Proxmox host storage — that keeps a dead NAS from hanging Proxmox itself, and you can reboot or move the one VM without touching the host. FYI, use nofail with automount rather than a plain entry that blocks boot, so the VM still comes up if TrueNAS is offline when it starts.
Give each Docker service its own dataset/share instead of one big share for everything, so one service filling or locking a share doesn’t take the rest down. And keep anything that can’t tolerate a stall — database files especially — on local disk in the VM, with only bulk media/files on the NFS mount. Test it once by taking TrueNAS offline on purpose and watching what the containers do; that’s when you’ll find out if a hang occured rather than a clean error. Seperate shares also make permissions easier to fix per service, since you’re already dealing with the ownership issues tofu mentioned.
Mount the NFS in the VM itself. If it is LXC make sure the container has the permissions set in Proxmox itself for it to be allowed to mount things like NFS and SMB.
No they are docker containers.
Mounting into the VM and then bindmount as the other commenter suggested is the most straightforward. The trickiest part will be Dataset ownership and permissions in TrueNAS so that the clients can read and write, but there’s tutorials for exactly that.
Mount it in the VM and then ensure the containers can write to the volumes. That will be quickest, easiest and most maintainable.