-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NFS provisioner fails #120
Comments
W.r.t. DNS issue, maybe you should try Rootless mode of k3s. It is based on Usernetes but includes DNS stuff by default. |
I would say the best bed for this is a fuse based nfs, since it is not likely that user namespace root is going to be allowed to mount an nfs share any time soon. Also NFS and User Namespace does not work well together if you are going to have multiple a process changing uids inside of an environment. Another potential option would be to setup automounter then the host kernel could mount directories on demand when a containerrized process entered the mount point. |
Hey, great project! I tried to get the helm nfs server provisioner running and ran into some roadblocks on a GCE centOS 8 machine.
First, just starting the helm chart with this config: (run through envsubst)
Afterwards, the necessary PV is created and a PVC is bound to nfs:
$nfspvcname
is set to the PVC created by NFS.Now the pod for nfs crashes continously:
Since the error seems to be related to missing DNS services I tried to setup kube dns via https://github.com/kelseyhightower/kubernetes-the-hard-way/blob/master/docs/12-dns-addon.md
I had to change the IP from 10.32.0.10 to 10.0.0.10, but the dns pod also fails:
Stderr of run.sh:
The text was updated successfully, but these errors were encountered: