Mounting NFS shared folders fails on MacOSX on vagrant 1.7.4

[alexortizrosado]

After going through the setup steps in the README for running locally, my vagrant instance fails to mount the NFS shared folders:

$ vagrant up
Bringing machine 'herokuwp' up with 'virtualbox' provider...
==> herokuwp: Box 'ubuntu/trusty64' could not be found. Attempting to find and install...
    herokuwp: Box Provider: virtualbox
    herokuwp: Box Version: >= 0
==> herokuwp: Loading metadata for box 'ubuntu/trusty64'
    herokuwp: URL: https://atlas.hashicorp.com/ubuntu/trusty64
==> herokuwp: Adding box 'ubuntu/trusty64' (v20150609.0.10) for provider: virtualbox
    herokuwp: Downloading: https://atlas.hashicorp.com/ubuntu/boxes/trusty64/versions/20150609.0.10/providers/virtualbox.box
==> herokuwp: Successfully added box 'ubuntu/trusty64' (v20150609.0.10) for 'virtualbox'!
'...
==> herokuwp: Configuring and enabling network interfaces...
==> herokuwp: Exporting NFS shared folders...
==> herokuwp: Preparing to edit /etc/exports. Administrator privileges will be required...
Password:
The nfsd service does not appear to be running.
Starting the nfsd service
==> herokuwp: 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' 192.168.50.1:'/Users/alexortiz/Development/heroku-wp' /app

Stdout from the command:



Stderr from the command:

stdin: is not a tty
mount.nfs: Connection timed out

I found this stackoverflow answer that seems to suggest the config format for setting up NFS mounts in version 1.6+ is different:

http://stackoverflow.com/questions/26700249/cannot-mount-vagrant-synced-folder-with-nfs

Found the solution for the problem here hashicorp/vagrant#2546

The correct syntax for vagrant version 1.3 to 1.6 is:

config.vm.synced_folder ".", "/vagrant", :nfs => { :mount_options => ["dmode=777","fmode=777"] }

I'm using a brand-new install of vagrant:

$ vagrant --version
Vagrant 1.7.4

I'm on MacOSX 10.10.3

[alexortizrosado]

I did some further digging and it seems that nfsd service is not started, despite what the startup log suggests:

$ vagrant ssh
$ sudo service nfs-kernel-server status
nfsd not running

When I try starting nfsd, it fails:

$ sudo service nfs-kernel-server start
 * Not starting NFS kernel daemon: no exports.

As the service startup message indicates, /etc/exports doesn't have any export NFS configs:

$ cat /etc/exports
# /etc/exports: the access control list for filesystems which may be exported
#       to NFS clients.  See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes       hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4        gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes  gss/krb5i(rw,sync,no_subtree_check)
#

[xyu]

I rebuilt the Vagrant environment in af3cd22 and we are now using the native shared folder implementation and not NFS. Hopefully this will make the file syncing more reliable. Seeing as we are not using NFS anymore I'm going to mark this as closed. Thanks for the report!