指定了winnfsd不正确的安装选项

Question

我正在开发一个带有Vagrant Box的WordPress网站" vccw-team/Xenial64＆quot"，可以在vccw.cc上找到。该网站的等待时间很慢，平均5秒钟，进行了一些谷歌搜索，许多人指向Vagrants同步文件夹，该文件夹与VirtualBox结合使用缓慢。解决方案：NFS。Windows上不存在NFS，因此引起了Vagrant插件Winnfsd。

我安装了插件并更改了VagrantFile：

  config.vm.network :private_network, ip: "192.168.33.10"
  config.vm.synced_folder _conf['synced_folder'],
      _conf['document_root'], :create => "true", :mount_options => ['dmode=755', 'fmode=644'], type: "nfs"

在流浪者上，我收到此消息：

==> vccw.dev: Mounting NFS shared folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -o vers=3,udp,dmode=755,fmode=644 192.168.33.1:/D/_projects/Vagrant/vccw/wordpress /var/www/html
Stdout from the command:

Stderr from the command:
mount.nfs: an incorrect mount option was specified

我猜是192.168.33.1:/d/_projects/vagrant/vccw/wordpress可能是错误的，因为d/_projects/_projects/vagrant/vccw/wordpress存在于主机上，而不存在于客人（192.168.33.1）。/p>

其他人设法使插件正常工作。有人知道我在做什么吗？

版本：

• vagrant：2.0.0
• vagrant-winnfsd：1.3.1
• VirtualBox：5.1.26 R117224（QT5.6.2）

Answer 1

i在vagrantfile中启用了dhcp：

  config.vm.network :private_network,  ip: "192.168.33.11",  type: "dhcp"

但这导致了错误：

NFS requires a host-only network to be created. Please add a host-only network to the machine (with either DHCP or a static IP) for NFS to work

然后，我在stackoverflow上的另一个问题中阅读了一个人可以通过在vagrantfile中使用以下代码来配置仅主机网络的问题：

  config.vm.network :private_network,  ip: "192.168.33.11"
  config.vm.network :public_network,  ip: "192.168.44.12"
  config.vm.synced_folder _conf['synced_folder'],
      _conf['document_root'], type: "nfs"

我认为192.168.44.0 255.255.255.0现在是托管网络，源自IP：" 192.168.44.12"。它现在工作了，我的WordPress网站的加载时间更快，平均约3秒钟。我很欣赏改进，但我会为其他调整而闻名。

额外的信息，来宾中的Ifconfig的输出：

vagrant@vccw:~$ ifconfig
enp0s3    Link encap:Ethernet  HWaddr 08:00:27:a8:df:8b
          inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fea8:df8b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1156 errors:0 dropped:0 overruns:0 frame:0
          TX packets:788 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:277602 (277.6 KB)  TX bytes:97056 (97.0 KB)
enp0s8    Link encap:Ethernet  HWaddr 08:00:27:da:65:a0
          inet addr:192.168.33.11  Bcast:192.168.33.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:feda:65a0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:12461 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7004 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10059912 (10.0 MB)  TX bytes:2671763 (2.6 MB)
enp0s9    Link encap:Ethernet  HWaddr 08:00:27:62:47:ec
          inet addr:192.168.44.12  Bcast:192.168.44.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe62:47ec/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:204 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:18654 (18.6 KB)  TX bytes:648 (648.0 B)
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:18 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:1658 (1.6 KB)  TX bytes:1658 (1.6 KB)