[SOLVED]: Can't get NFS permission working without TrueNAS CLI

TrueNAS General
1

CONTEXT

TrueNAS:

  1. User: navidrome (5001)
  2. Group: navidrome (5000)

Navidrome Proxmox LXC unprivileged no-nesting container:

  1. User: navidrome (5001)
  2. Group: navidrome (5000)

ISSUE

No matter what I do, the permission doesn’t work UNLESS:

TrueNAS CLI:

chown -R 105000:105001 /mnt/personal/Music

Then everything works, files get mapped to navidrome:navidrome but this can’t be right, I shouldn’t have to use TrueNAS CLI to set the permission.

This is also the only way I got Jellyfin LXC unprivileged no-nesting container working but again, sure it works but this can’t be right.

Navidrome:

Edit permission from Dataset > Permission: Doesn’t work
Shares > Edit NFS > Maprootuser/Maprootgroup: Doesn’t work.

I must be making a rookie mistake, I wanna get things right this time.

Thanks a lot for any help/recommendation.

2

I ditched NFS and to be honest, I should have looked into this sooner.
It also gives me more flexible control.

On my Linux PC, I mount it as the LXC user so all files are created with that ownership, but mapped to my local user. All outside of TrueNAS.

//nas01.home.arpa//Music /home/user/Music cifs username=navidrome,password=navidrome,uid=1000,gid=1000,_netdev,nofail 0 0

I did the same on Proxmox and it gets mapped inside the LXC with the correct user.
Pretty much how I was doing via NFS but way way way more flexible.

I wished I had looked into this before, I do not move insane amount of data to justify NFS, I only use Linux but couldn’t be happier with SMB.