When "Vagrant Up" It Says "It Appears Your Machine Doesn't Support Nfs" (Debian Jessie)

When “vagrant up” it says “It appears your machine doesn't support NFS” (Debian jessie)

Can be fixed by adding any exports to /etc/exports.

by :

   modprobe nfs
   modprobe nfsd

then running vagrant, which will add /etc/exports, then reloading
kernel-server and restarting vagrant.

issue http://jb-blog.readthedocs.io/en/latest/posts/0021-vagrant-nfs-problems.html

instead of installed NFS cos really no supported :

Try just removing type: nfs from the vagrant_synced_folders

More : https://www.vagrantup.com/docs/synced-folders/nfs.html

Using NFS with vagrant doesn't work

Downgrading and changing the base image to be an LTS Ubuntu (as opposed to XUbuntu) seemed to fix this.

NFS Fails after packaging a Vagrant box

I had the very same problem, but I have figured it out. At least it works for me now. :)

TL;DR:

• Check /etc/exports for syntax errors and recreate /etc/exports with an entry you make sure works.
• Verify network interfaces on the box are initialized correctly (check /etc/network/interfaces and run ifconfig -a).
• At least Debian and Ubuntu store information about the persistent network device in /etc/udev/rules.d/70-persistent-net.rules. If you see that eth1 is initialized as eth2 it is because the mac adress of the network card is regenerated when you create a new box instance. rm /etc/udev/rules.d/70-persistent-net.rules and repackage your box.
• If you are unable to repackage your box update /etc/network/interfaces to use eth2 instad of eth1

Long form:

• Vagrant is 1.0.1
• OS X is 10.7.3
• Box is custom Debian Wheezy 64.

When reloading or recreating the box it would die on NFS mount with the typical message.

[default] Mounting NFS shared folders...
Mounting NFS shared folders failed. This is most often caused by the NFS
client software not being installed on the guest machine. Please verify
that the NFS client software is properly installed, and consult any resources
specific to the linux distro you're using for more information on how to
do this.

Inspecting the /etc/exports file with NFS Manager it tells me my /etc/exports contain syntax errors.

I clean out /etc/exports and test nfs client and server with this entry:

/Users/tm/git -alldirs localhost 33.33.33.10

When running vagrant up NFS mounting is working again.

When repackaging box after apt-get dist-upgrade I noticed the NFS folders would not mount again.

This time there were no errors in the /etc/exports file. I discovered Vagrant had not initialized the host local interface.

/etc/network/interfaces contained this:

#VAGRANT-BEGIN
# The contents below are automatically generated by Vagrant. Do not modify.
auto eth1
iface eth1 inet static
    address 33.33.33.10
    netmask 255.255.255.0
#VAGRANT-END

ifconfig -a returned this:

eth0      Link encap:Ethernet  HWaddr 08:00:27:3a:47:72  
      inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
      inet6 addr: fe80::a00:27ff:fe3a:4772/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:971 errors:0 dropped:0 overruns:0 frame:0
      TX packets:614 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000 
      RX bytes:83951 (81.9 KiB)  TX bytes:74872 (73.1 KiB)

eth2      Link encap:Ethernet  HWaddr 08:00:27:89:f5:e3  
      BROADCAST MULTICAST  MTU:1500  Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000 
      RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

The interface was not defined correctly.
After updating the /etc/network/intefaces stanza to use eth2 NFS mounting is working again.

How do I get vagrant halt to successfully shut down debian jessie vm on yosemite host?

This was a bug in vagrant, here is the pull request that fixed it:

https://github.com/mitchellh/vagrant/pull/6315

Version 1.7.5 will include this fix.

Vagrant up - read error

I can't seem to reproduce your error:

$ vagrant init migosm/debian-7.6-kernel-3.16
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'migosm/debian-7.6-kernel-3.16' could not be found. Attempting
to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Loading metadata for box 'migosm/debian-7.6-kernel-3.16'
    default: URL: https://atlas.hashicorp.com/migosm/debian-7.6-kernel-3.16
==> default: Adding box 'migosm/debian-7.6-kernel-3.16' (v1.0.5) for provider: v
irtualbox
    default: Downloading: https://atlas.hashicorp.com/migosm/boxes/debian-7.6-ke
rnel-3.16/versions/1.0.5/providers/virtualbox.box
    default: Progress: 100% (Rate: 7909k/s, Estimated time remaining: --:--:--)
==> default: Successfully added box 'migosm/debian-7.6-kernel-3.16' (v1.0.5) for
 'virtualbox'!
==> default: Importing base box 'migosm/debian-7.6-kernel-3.16'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'migosm/debian-7.6-kernel-3.16' is up to date...
==> default: Setting the name of the VM: SO_test_default_1427480182231_55057
==> default: Fixed port collision for 22 => 2222. Now on port 2203.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 => 2203 (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2203
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if its present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
    default: /vagrant => C:/HashiCorp/Vagrant/SO_test
$ vagrant ssh
Linux packer-debian-7 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) x8
6_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Jan  4 16:49:00 2015 from 10.0.2.2
vagrant@packer-debian-7:~$

This answer to a question about the same SSL error suggests that the error message is telling you that the host is forcibly closing the connection for some reason. This could be because the Atlas servers were struggling with load during the time you were trying it and started dropping connections. Alternatively your connection may have been running for too long and it was forcibly closed by the web server.

In this instance you might be best using a download manager and directly downloading the box file and then using vagrant box add [box file path] to use the box. It does mean that you can't keep up to date with any changes to the box on the Atlas servers but should be fine otherwise.

---

Related Topics