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.
this post was submitted on 31 Oct 2026
16 points (100.0% liked)
Selfhosted
63722 readers
798 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
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.
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.
Ok, that sounds neat. I have a large dataset shared with proxmox to save snapshots of the VMs. Is there a setting in proxmox that will prevent it hanging if the share goes down? Also, if i have 5 services on vm, do i need 5 top level datasets on TN or can i nest in a "proxmox_services" datset, which would be easier to maintain and setup for replication, rsync, etc?