Backup storage mount nfs creates files with nobody user account (can we mount with nfs auth?)

I’m trying to use the automated backups function with NFS. I set up a new NFS storage location the other day and even though I set it as an included backup target, no files were being dropped on the remote server.

I just tried turning off the “local system” option and manually creating an automated backup and it failed to create the file. I went to the host’s filesystem and made the directory writable by everyone drwxrwxrwx and tried it again. The file was created, however, it was owned by nobody in nogroup:

(base) spikeygg@remote:/backup/hassio_backups$ ls -la
total 814704
drwxrwxrwx 2 spikeygg users         4096 Feb  2 09:09 .
drwxrwxr-x 8 spikeygg users         4096 Jan 25 10:19 ..
-rw-r--r-- 1 nobody   nogroup  834242560 Feb  2 09:09 8c4ba615.tar
(base) spikeygg@remote:/backup/hassio_backups$

Is there some way to have the NFS share mounted via a specified username so that the files created by the backups aren’t anonymous? According to the Common tasks - Operating System - Home Assistant only the CIFS shares allow username/password assignments. :frowning: