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
mount.nfs: requested NFS version or transport protocol is not supported #122
Comments
After finding this on the Arch Wiki I've solved this problem which I've also had with some other boxes. But the problem still persists around this Kali box. This is the other error which I get now:
|
Hello @alincocio, sorry for not responding sooner normally the GitHub mobile app notifies me if there was an issue on one of my repos and it didn't 🤔. Sorry about that! So, I actually have run into this issue on a few different machines before ( at least it looks familiar ). I think it is a version miss match between a vagrant default (using v3 of nfs for shared folders) and your OS. The vagrant box should support v4 out of the box (from a client (inside the VM) perspective), but its a matter of using the right version when connecting to the "server" (i.e. your host machine that is running the VM). If you don't mind me asking, what distro are you running? ( Fedora, Ubuntu, arch, etc...) If it is the issue that I am thinking of, then you might have to fiddle around with some options inside of your Vagrantfile. I wish I could change this on the "server" side, but then that might break compatibility for other distros that don't have a more updated nfs setup. This should be an example of what you could add to your Vagrantfile to (hopefully) fix the issue: config.vm.provider :libvirt do |lv, override|
override.vm.allowed_synced_folder_types = [:libvirt, :nfs]
override.vm.synced_folder ".", "/vagrant", nfs_version: 4, nfs_udp: false
end Here is an example of me using it when I actually do development for this repo. Let me know if this helps at all or what other errors you have 🙂 |
another thing I do for debugging is (when I am having an issue inside the vagrant box on libvirt (libvirt specifically, because it destroys the box if it fails)) run One such command you could run to help diagnose is the command that vagrant is outputting that it had an error with. mount -o vers=3,udp 192.168.121.1:/home/me/Learning-Linux/vagrant-boxes/kali /vagrant Then once you can get it to mount properly you can just modify the Vagrantfile to adapt to using the same stuff (i.e. nfs version 4, etc... ). |
Thank you indeed 👍🏽 This block of code indeed did the trick. That's much appreciated for taking the time to look into it 😄 Keep up the good work! 💯
|
That's awesome @alincocio ! I am glad it is working now 😁
Anytime 😊
Thank you for using my vagrant box 🙂! You are the first person (besides me 🙃) to file an issue that isn't a co-worker, so thank you for reaching out! I'm glad to know someone else beside my co-workers use it and enjoy it 😅😁 |
Hello there,
I'm trying to get your box running via
vagrant
, havinglibvirt
as provider.This is the output that I get...
** What can I do to fix it? Could this feature be implemented on your side? So we would be able to mount NSF shared folders right out of the box?
I guess the box needs to have NFS version 4 and above installed.
The text was updated successfully, but these errors were encountered: