So basically you just built a small XO VM instead of running it in Docker? I had originally been thinking of making a small VM to run XO in a container there - just because Docker containers are super easy to keep updated and I could run some other orchestration-y stuff there too, like Rancher - but if you're saying that's a non-starter I'll just bite the bullet and build a tiny VM dedicated to XO and be very grateful to you for having saved me a lot of frustration.

I'm just a home / homelab user, but always impressed with the community around XCP-NG too and have learnt a huge amount from Lawrence Systems.

Anyway this morning I have a successful backup completed :

Thanks again.

In the end, following a permissions reset and forcing the NFS share to squash and use my user/group ID I think I have progress. I can see it is writing to the NFS share.

Then I got : EEXIST: file already exists, open '/run/xo-server/mounts/6299d107-2aa2-41bf-bfd7-2f487ff5422f/xo-vm-backups/801e2b10-5c7d-b7af-ad5e-fbcc83e47d5b/.20220930T221548Z.xva'

A quick google led me to this being related to nfs 3. I switched to NFS 4 then I got path not found.

Not sure why, but I tried removing "export" from the path and it worked.

It does appear now to be running a backup job .... fingers crossed.

What a mine field!

Thanks for all the pointers.

What is the IP address of the host that is running XO?

The docker container will need the SYS_ADMIN capability to do NFS mounts.

Sorry to have taken up your time, but thanks very much for your help!
At least i have a clear direction to google now.

One thing I can say, is that it is working on my host so it must be something about my XO setup trying to talk to it. which may well still be permissions.

/etc/sudoers?

@daninmanchester said in XO Remote mount.nfs: access denied by server while mounting:

"stderr": "mount.nfs: access denied by server while mounting 192.168.11.60:/Backups",

Would appear to be a rights issue to me.

@tjkreidl verified they can be seen :

Export list for 192.168.11.60:
/export/Backups 192.168.11.0/24
/export/Everyone 192.168.11.0/24
/export 192.168.11.0/24

do you need to add "/export" (/export/Backups ) to be able to find the right path?

It doesn't output any more than I shared last time :

bash-5.1# showmount -e 192.168.11.60
Export list for 192.168.11.60:
/export/Backups 192.168.11.0/24
/export/Everyone 192.168.11.0/24
/export 192.168.11.0/24
bash-5.1#

It just occurred to me, I'm running XO in a docker not direct on the host. Do I need some network config to enable NFS?

I don't touch things manually, it's done through OMV. This is the exports file. I don't have any multipathing as far as I know. It's not something I've set up.

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

# /etc/exports: the access control list for filesystems which may be exported
#               to NFS clients.  See exports(5).
/export/Everyone 192.168.11.0/24(fsid=94a977de-432c-4653-9870-a1cd0a83110d,ro,subtree_check,insecure,crossmnt)
/export/Backups 192.168.11.0/24(fsid=bb941285-c5d8-492d-9b49-43a2dc30557c,rw,all_squash,insecure,async,no_subtree_check,anongid=100,crossmnt)

# NFSv4 - pseudo filesystem root
/export 192.168.11.0/24(ro,fsid=0,root_squash,no_subtree_check,hide)
/export 192.168.11.70(ro,fsid=0,root_squash,no_subtree_check,hide)

Export list for 192.168.11.60:
/export/Backups 192.168.11.0/24
/export/Everyone 192.168.11.0/24
/export 192.168.11.0/24

I'm using the following options at present, but have tried with various users and groups, etc.

rw,all_squash,insecure,async,no_subtree_check,anongid=100,crossmnt