Hi there, I’m having problems with sharing folders on Windows 10 Pro.
If I install vagrant-winnfsd then Vagrant hangs at mounting nfs shared folders . . .
If I uninstall this plugin everything seams to be ok.
Then if I try to change the type from ‘nfs’ to “smb” in vagrant.default.yml it crashes too.
I don’t know if there is a way to make it work or if I’ll have a performance problem working with this configuration.
Virtual Box - 5.2.22
vagrant - 2.2.2
Than you very much in advance.
Vagrant 2.2.2 has some known issues (w/ Windows). Downgrading Vagrant to 2.1.1 should do the trick
Hi @Henk, thanks for your answer.
As I registered these versions in this post and it worked perfectly, I had already tested it unsuccessfully with Vagrant 2.1.5.
I’ve just tested it again with Vagrant 2.1.1 and it fails at the same point.
The strange thing is that it indicates IP - 192.168.50.1 and I don’t know why.
Stderr from the command:
mount.nfs: requested NFS version or transport protocol is not supported
ERROR vagrant: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -o vers=3,udp,vers=3,udp,nolock 192.168.50.1
I stumbled upon this (and it surprised me):
Windows users: NFS folders do not work on Windows hosts. Vagrant will ignore your request for NFS synced folders on Windows.
P.S. I’m succesfully running Vagrant 2.1.1 on a Windows 10 Pro host w/ VMware Workstation Pro 14 and the following Vagrant plugins:
What versions of vagrant plugins are you running?
Hi @Henk and thank you for your help.
ok, you’re using VMware.
As I said above, the last time I tried to launch a Trellis project I used Virtualbox and It worked - post, but it was on Windows 10 Home not Windows 10 Pro.
These are the plugins versions I’m using now:
I didn’t know vagrant-share, I’m testing with it installed.
vagrant.default.yml is not
192.168.50.1, try updating your Windows
known_hosts file for the IP address in
I’ve just checked it and there is no entry for a vagrant VM, neither
This topic was automatically closed after 42 days. New replies are no longer allowed.