https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
c
I’m sorry, you’re saying that for some reason you’re mounting an nfs volume at /var/lib/rancher/k3s/data/current/bin/aux/ ?
or are you saying that the bundled mount command doesn’t work with nfs v4?
a
nope i'm saying that k3s is using the bundled mount
yes exact
it's working only when -o vers=4.0 is used
c
wait so it works if you explicitly ask for v4, but if you use the default v3 the bundled mount command does not work?
a
and there is no possibility to define nfs version to use when mounting volume to pod
yes seems like without option is trying to use v3
c
that is not true
Copy code
kind: PersistentVolume
metadata:
  name: example
spec:
  mountOptions:
    - hard
    - nfsvers=4.1
a
I found that it's possible only with PVC
c
yes, are you not using pv/pvc?
a
I'm not, nfsVolume is mounted to pod without pv
c
why not just define an NFS PV and mount that instead?
🎯 1
if you for some reason must keep using the legacy volume then removing the bundled mount command is probably a good workaround, although as you said you’ll have to keep doing that on every host after every upgrade. Is that easier than migrating over to nfs PVs?
a
well we can define an NFS PV instead, but we will need to refactor a lot...
for us it will be easier to remove the bundled mount even if it's after every upgrade
Just wanted to make sure that bundled mount removing will not cause to others issue
Also maybe for next release mount bundled can be moved to 
bin/
or is it intentionally in 
bin/aux/
?
c
/bin is ALWAYS in the path, /bin/aux is only in the path if you set --prefer-bundled-bin. So from your perspective, moving it to bin would be worse.
a
Many thanks !! (I'll use pv instead)
2 Views
Open in Slack
PreviousNext
Powered by