inman.turbo
Contributor
- Joined
- Aug 27, 2019
- Messages
- 149
So the problem is the service attempts to mount the path to the claim which is created under the shared dataset, rather than mounting the dataset directly. How would one get this working?
In this case the actual share or dataset is @ /mnt/Pool2/playground/ which where the dynamic storage class has it mounted when it created the default-gitea-volume-claim-pvc-cb290896-7c89-4b44-97fa-2efcd5a69553 for the gitea service.
On a linux nsf server it can work using `no_root_squash` and `insecure` options on the export. I have no idea how to get this working with freenas and can't find any references to help with it. Security is not a concern in this case this is a firewalled development environment.
Code:
mount.nfs: access denied by server while mounting nas2.localdomain:/mnt/Pool2/playground/default-gitea-volume-claim-pvc-cb290896-7c89-4b44-97fa-2efcd5a69553
In this case the actual share or dataset is @ /mnt/Pool2/playground/ which where the dynamic storage class has it mounted when it created the default-gitea-volume-claim-pvc-cb290896-7c89-4b44-97fa-2efcd5a69553 for the gitea service.
On a linux nsf server it can work using `no_root_squash` and `insecure` options on the export. I have no idea how to get this working with freenas and can't find any references to help with it. Security is not a concern in this case this is a firewalled development environment.
Last edited: