mount.nfs: requested NFS version or transport protocol is not supported

[techsk8]

mount.nfs: requested NFS version or transport protocol is not supported

[techsk8]

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! 💯

 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

[techsk8]

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:

THe same output as above ^^^^^^
....
.....
==> kali: Exporting NFS shared folders...
==> kali: Preparing to edit /etc/exports. Administrator privileges will be required...
==> kali: Mounting NFS shared folders...
==> kali: Pruning invalid NFS exports. Administrator privileges will be required...
==> kali: Removing domain...
==> kali: Deleting the machine folder
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mount -o vers=3,udp 192.168.121.1:/home/me/Learning-Linux/vagrant-boxes/kali /vagrant

Stdout from the command:



Stderr from the command:

mount.nfs: an incorrect mount option was specified

VM must be created before running this command. Run `vagrant up` first.

[elreydetoda]

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 🙂

[elreydetoda]

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 vagrant up with the --no-destroy-on-error flag. Then it won't remove the box from my machine, and I can hop in to run different commands to further diagnose the issue.

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... ).

[elreydetoda]

Thank you indeed 👍🏽

This block of code indeed did the trick.

That's awesome @alincocio ! I am glad it is working now 😁

That's much appreciated for taking the time to look into it 😄

Anytime 😊

Keep up the good work! 💯

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 😅😁