I found the issue, it was me!! LOL I thought it had to be a setting I had forgotten and it was, I forgot to enable NFS & Nesting under Features in the Otions of the cotainer, see this image - https://imgur.com/bSiozKS
Thank you to everyone that took the time to reply and offer their suggestions.
Hi All,
Let me start with some basic basic background on my set up, I have a server running Proxmox with some Ubuntu containers. I have a separate server running TrueNas with a share that has both NFS & SMB set up. I can see this share in Windows 11 and read and write to it.
One of the Ubuntu containers is able to see this share via NFS and read and write to it too. I am testing Sonarr, Prowlarr & Qbittorrent Docker containers and got the basics set up, Sonarr can find episodes via Prowlarr of a TV show, hand it off to Qbittorrent to download and then move it from the download folder to the TV folder. Both the download folder and the TV folder are on the TrueNas server.
I then set up a Docker container for AudioBookShelf in the same Ubuntu CT and that can also read and write to the NFS share.
My issue is that I tried to set up another Ubuntu CT on the Proxmox server but cannot seem to access the NFS share on the TrueNas server.
This is what I did (which I think was the same process as the working CT)
1/Create a privileged conatiner
2/ Update and upgrade the CT
3/ Install nfs-common
4/ Create a directory in the CT in the /mnt directory for the NFS share
5/ added this line to the fstab file in /etc 192.168.0.188:/mnt/store/test-share /mnt/test-share nfs defaults 0 0
However, when I run mount -a I get this error message mount.nfs: access denied by server while mounting 192.168.0.188:/mnt/store/test-share
Running df -h does not show the mount obviously but it does in the working CT
As a further test, I cloned the working CT, deleted all the Docker containers and I can still see the NFS just fine.
I have probably missed a step while setting up the new CT but I’m not sure what.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
Add “-vvv” to your mount command and see what else it tells you.
Hi, thanks for your reply.
when I run
mount -a -vvvI get the following:mount.nfs: timeout set for Tue Aug 8 16:14:10 2023mount.nfs: trying text-based options 'vers=4.2,addr=192.168.0.188,clientaddr=192.168.0.116'mount.nfs: mount(2): Permission deniedmount.nfs: trying text-based options 'vers=4,minorversion=1,addr=192.168.0.188,clientaddr=192.168.0.116'mount.nfs: mount(2): Permission deniedmount.nfs: trying text-based options 'vers=4,addr=192.168.0.188,clientaddr=192.168.0.116'mount.nfs: mount(2): Permission deniedmount.nfs: trying text-based options 'addr=192.168.0.188'mount.nfs: prog 100003, trying vers=3, prot=6mount.nfs: trying 192.168.0.188 prog 100003 vers 3 prot TCP port 2049mount.nfs: prog 100005, trying vers=3, prot=17mount.nfs: trying 192.168.0.188 prog 100005 vers 3 prot UDP port 661mount.nfs: mount(2): Permission deniedmount.nfs: access denied by server while mounting 192.168.0.188:/mnt/store/test-share