To have write access to a NFS share hosted on OMV VM, hosted on the same proxmox machine.

[garzzz]

Hi,

Long story short: if i have a NFS shared folder that i'm able to mount from and OMV VM into proxmox, but i can only read it, the issue is in the proxmox config or in the OMV config?

More details:
i've hosted a virtualized NAS before, with disk passthrough through PICe, and i'm very happy with this solution to provide NAS services to my network.
Then i wanted to expand the server capabilities, adding an *arr stack.

I choosed to host several LXC container, one for every arr app, and i thought i've solved the issue to provide access to the shared folder on the virtualized NAS.
I've read that a proper solution is to mount the NFS share directly on proxmox, and then use bind mount points to provide access to the LXC containers.

I've read the documentation and understood how to do so, now proxmox mount the NFS folder (after a delay, to let OMV boot properly) and the containers have their bind mountpoints.

The only issue is that they only have read access, they can't write.
Of course (not really, i didn't thought about it at the beginning) they can't, since even proxmox itself can't write that folder.

My NFS knowledge is limited, i don't understand why i can't write on that folder, my guess is that i'm using "root" user to try to access (but on the other hand i don't know how to allow an external root user and, most important, if this is the proper way to solve it.

 

[louie1961]

It's a problem on the OMV side. You probably have permissions set incorrectly

 

[garzzz]

Thanks, i'll check OMV.

But i've read that the only way to assign NFS permission is to match UID/GID, from proxmox to OMV.
This seems to be quite easy, for a normal user. But do i have to provide root access to the shared folder?

I have the NAS only working in LAN, but still make "root" the owner of a shared service doesn't sound good to me.

Is NFS a good sharing option to provide data storage to a proxmox machine and containers or is there something better? (possibly, not way more complex).

 

[louie1961]

But i've read that the only way to assign NFS permission is to match UID/GID, from proxmox to OMV.
This seems to be quite easy, for a normal user. But do i have to provide root access to the shared folder?
.

That hasn't been my experience. You can map users in your NFS settings in OMV. In fact this isn't unique to OMV, its an NFS feature. You can map root to a regular user, and visa versa

When your create your share (or you can update a share) you get a screen like this


Make sure its not read only. AND under extra options, you can use root_squash, or I use all_squash, then I add "anonuid=1001,anongid=100" and set the uid and gid to match a user I created especially for Proxmox. There's a lot of ways to skin a cat though. On one of my other OMV instances I use these options: no_subtree_check,insecure,no_root_squash. Just make sure you give root read write access in your ACL for the share

 

[louie1961]

And for the record, I find managing NFS shares, ACLs and permissions a lot easier to handle on OMV versus TrueNAS

 

[garzzz]

Make sure its not read only. AND under extra options, you can use root_squash, or I use all_squash, then I add "anonuid=1001,anongid=100" and set the uid and gid to match a user I created especially for Proxmox.

Thanks a lot, i've managed to have the shared folder writable with:

subtree_check,insecure,all_squash,anonuid=0,anongid=0

i'll have to study more the ACLs for the different metodologies since it's not very clear to me, especially the possible safety concerns.
But for now i think i'm fine, since it's only an home lan share.

Thanks again.