Comment on Help With NFS Share To Proxmox Container
TheDevil@lemmy.world 1 year ago
The two docker containers can access the share, but the new proxmox container can’t?
The new proxmox container will have a different IP. My guess would be that the IP of the docker host is permitted to access the nfs share but the ip of the new proxmox container is not.
To test, you can allow access from your entire lan subnet (192.168.1.1/24)
SonyJunkie@lemmy.world 1 year ago
Hi, thanks for your reply.
Lets call the original Proxmox container CT1 and this has the *arrs Dockers that can access and interact with the NFS share on TrueNAS
Lets call the new Proxmox container CT2 and this is the one giving me the can’t access error
Lets call the cloned Proxmox container CT1Clone, this one can access the NFS share.
I think the NFS share is not restricted to any IP address, this is a screenshot of the NFS permissions. i.imgur.com/9k5jnw4.png I can also access if from my Windows machine that also has a different IP address.
CT1 & CT1Clone work fine, CT2 doesn’t work.
TheDevil@lemmy.world 1 year ago
You can ignore the windows machine unless it’s using nfs, it’s not relevant.
Your screenshot suggests my guess was incorrect because you do not have any authorised Networks or Hosts defined.
Even so if it was me I would correctly configure authorised hosts or authorised networks just to rule it out, as it neatly explains why it works on one container but not another. Does the clone have the same IP by any chance?
The only other thing I can think for you to try is to set maproot user/group to root/wheel and see if that helps but it’s just a shot in the dark.
SonyJunkie@lemmy.world 1 year ago
Hi,
The clone has a different IP address