NFS shared folders failing to mount

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

NFS shared folders failing to mount

Adam Duro
I am mounting three different folders from my host to a VirtualBox VM. Here is what my NFS config statements look like:

config.vm.synced_folder "./Ace-CMS", "/opt/tennis-ace/current", :nfs => true, :uid => 'vagrant', :gid => 'vagrant'
config.vm.synced_folder "./Ace-CMS-Static", "/opt/tennis-static/current", :nfs => true, :uid => 'vagrant', :gid => 'vagrant'
config.vm.synced_folder "./enetpulse", "/opt/enetpulse_php/current", :nfs => true, :uid => 'vagrant', :gid => 'vagrant'

When I do a vagrant up, I get the following error on mount:

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -o udp,vers=3 192.168.121.1:'/Users/adamduro/Workspace/projects/tennis.com/Ace-CMS' /opt/tennis-ace/current
Stdout from the command:


Stderr from the command:
stdin: is not a tty
mount: wrong fs type, bad option, bad superblock on 192.168.121.1:/Users/adamduro/Workspace/projects/tennis.com/Ace-CMS,
       missing codepage or helper program, or other error
       (for several filesystems (e.g. nfs, cifs) you might
       need a /sbin/mount.<type> helper program)
       In some cases useful info is found in syslog - try
       dmesg | tail  or so
I am running Vagrant 1.2.5 on OS X 10.8.2, and I am launching the following opscode/bento box:

https://opscode-vm.s3.amazonaws.com/vagrant/opscode_ubuntu-12.04_provisionerless.box

Any help is appreciated.

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.