It works fine. I do it. I mount the services share to /mnt/data on the host and then just path mount /mnt/data/servicename to the container.
Some of my containers I also mount to directly using NFS volumes in the docker compose. This is for things that generally aren't service data, like media.
Both is fine. Maintaining different datasets has the administrative overhead you mentioned, but can have security benefits, e.g. if you use different users in the different docker services and adjust the NFS permissions correspondingly. If service A gets hacked and escapes the container but doesn't get privilege escalation, it can't access the other services' data.
This is independent of which version you choose, but check whether adding some storage to Proxmox is an option. Having TrueNAS as a runtime dependency for all your services can get annoying real quick.
I have nfs shares on my truenas for my docker containers on proxmox. I put the info in my guest's fstab and they usually mount at boot to /srv folders I created and specified.
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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!