NFS Verwendung mit vagabundierenden nicht

Question

funktioniert Ich habe

==> default: 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' 10.0.0.1:'/Users/wayne/app' /vagrant 

Stdout from the command: 



Stderr from the command: 

stdin: is not a tty 
mount.nfs: access denied by server while mounting 10.0.0.1:/Users/wayne/app 

Ich brauche dann vagrant reload und es scheint Arbeit ... Aber das sollte ich doch nicht tun müssen?

[aktualisiert: log output]

INFO retryable: Retryable exception raised: #<Vagrant::Errors::LinuxNFSMountFailed: The following SSH command responded with a non-zero exit status. 
Vagrant assumes that this means the command failed! 

mount -o 'vers=3,udp' 10.0.0.1:'/Users/wayne/sonatribe' /vagrant 

Stdout from the command: 



Stderr from the command: 

stdin: is not a tty 
mount.nfs: requested NFS version or transport protocol is not supported 
> 
INFO ssh: Execute: mount -o 'vers=3,udp' 10.0.0.1:'/Users/wayne/sonatribe' /vagrant (sudo=true) 
INFO retryable: Retryable exception raised: #<Vagrant::Errors::LinuxNFSMountFailed: The following SSH command responded with a non-zero exit status. 
Vagrant assumes that this means the command failed! 

mount -o 'vers=3,udp' 10.0.0.1:'/Users/wayne/sonatribe' /vagrant 

Stdout from the command: 



Stderr from the command: 

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

Answer 1

Downgrading und die Änderung der Basis-Image ein LTS Ubuntu zu sein (im Gegensatz zu Xubuntu gegen) schien dies zu beheben.

Answer 2

Für Linux Ich tue dies in der Host-Maschine:

systemctl stop nfs-kernel-server.service 
systemctl disable nfs-kernel-server.service 
systemctl enable nfs-kernel-server.service 
systemctl start nfs-kernel-server.service 

Answer 3

Es aufgrund passieren könnte VirtualBox und Guest Additions Versionskonflikt hosten. In diesem Fall kurz vor der Fehlerzeile in Ihrem Startprotokoll, sollen Sie immer sein:

==> default: Checking for guest additions in VM... 
    default: The guest additions on this VM do not match the installed version of 
    default: VirtualBox! In most cases this is fine, but in rare cases it can 
    default: prevent things such as shared folders from working properly. If you see 
    default: shared folder errors, please make sure the guest additions within the 
    default: virtual machine match the version of VirtualBox you have installed on 
    default: your host and reload your VM. 
    default: 
    default: Guest Additions Version: 5.0.26 
    default: VirtualBox Version: 5.1 

In meinem Fall Aktualisierung VirtualBox auf die neueste Version das Problem behoben.

Alternativ können Sie sicherstellen, dass die richtige Guest Addition Version vbguest Vagrant-Plugin auf dem Host-Computer installiert ist, mit:

vagrant plugin install vagrant-vbguest