missing NFS support error on Ubuntu hosts could be improved perhaps

[rubiojr]

@mitchellh, I'm just nitpicking but perhaps the missing NFS support error could be improved in Ubuntu hosts?

The error reads:

There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* It appears your machine doesn't support NFS, or there is not an
adapter to enable NFS on this machine for Vagrant. Please verify
that `nfsd` is installed on your machine, and try again. If you're
on Windows, NFS isn't supported. If the problem persists, please
contact Vagrant support.

nfsd is MacOSX specific (I think) and installing nfs-common package is good enough to make Vagrant 1.1.5 happy in Ubuntu (apparently). Since nfs-common isn't installed by default in Ubuntu installs, I guess this 'issue' will bite more people.

Since the package name is Ubuntu specific and Fedora, RHEL, whatever may need other packages, perhaps adding a link to a KB/wiki article or FAQ in the error output, listing this and recommending a 'fix' may be a good idea?

[mitchellh]

I wanted the most generic error message possible, I think this is the most generic since I quite literally need the NFS daemon. Perhaps I can say "NFS daemon" instead. It would be difficult to maintain a list to KB/Wikis for NFS for every distro.

I'm happy to look at pull requests to re-word this. :)

[rubiojr]

Thanks @mitchellh, I can definitely understand that.

Since you distribute debian packages for Vagrant, how about adding nfs-common dependency to it?

[dkrikun]

As I'm brand new to Vagrant and NFS, I got hooked with this error message and tried all kinds of apt-get install nfsd. Actually, this page was the first to come up when I googled for vagrant nfs ubuntu

[vnavanee]

apt-get install nfs-common works in ubuntu

[dixonge]

nfs-common is already the newest version

and yet I'm getting the "your machine doesn't support NFS" error on a simple 'vagrant up' command

Ubuntu 12.04 LTS

[pkill37]

$ sudo apt-get install nfs-common nfs-kernel-server worked for me on Ubuntu 13.10.

[therobyouknow]

@faviouz - this worked for me too on Ubuntu 12.04 LTS 64bit - thanks both are needed, not just nfs-common. When I had only installed nfs-common, I got this error:

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mount -o 'vers=3,udp' 33.33.33.1:'/home/hostmachinevagrantfolder/sites' /var/www

Stdout from the command:

Stderr from the command:

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

Once I installed nfs-kernel-server too, this error did not occur

So yes, use:
sudo apt-get install nfs-common nfs-kernel-server

I am using VirtualBox 4.3.2 with Vagrant 1.3.5
Yes I know there are later versions of both but from experience with Mac and Windows, certain version combinations don't work (fatal errors) but I will try the later versions at some point. Sometimes I find that the latest and greatest virtualbox sometimes has regression.

[j3rrey]

same here, u need both

sudo apt-get install nfs-common nfs-kernel-server

[Jose-27]

run this works for Ubuntu 15.10
sudo apt-get install nfs-common nfs-kernel-server

[thafner]

$ sudo apt-get install nfs-common nfs-kernel-server also works for me on Ubuntu 16.04

[corysimmons]

Just reiterating @faviouz original comment for the thumbs up karma.

sudo apt-get install nfs-common nfs-kernel-server

[markl17]

what exactly does one add to vagrantfile to get it of the ground all of these are post commands how about plain vagrant syntax
slave.vm.provider "virtualbox" do |vb|
vb.memory = $ucp_slave_memory
end
i can add this line inside vagrant file sudo apt-get install nfs-common nfs-kernel-server but still it doesnt comeup

[inoas]

OS X 10.11/10.12

For me the solution was to change whatever export PATH= saying to export PATH="/sbin:... whatever it was saying before because nfsd was actually installed and running but somehow vagrant didn't find it.

mate ~/.bash_profile; # instead of mate you can use: open, vim, atom, etc

Change export PATH= saying to export PATH="/sbin:

source ~/.bash_profile;
vagrant up;

---

BUT, I suppose the more secure-by-default solution is to add a symbolic link like so:

ln -s /sbin/nfsd /usr/local/sbin/nfsd

[johackim]

On arch linux: pacman -S nfs-utils

[jkobus]

just to confirm, this command still works on Ubuntu 17.10
sudo apt-get install nfs-common nfs-kernel-server

[JimiPedros]

I've tried sudo apt-get install nfs-common nfs-kernel-server on Ubuntu 14.04 trusty and i'm still gettingt the same error

[ghost]

This command works still works on Ubuntu 18.04:

sudo apt-get install nfs-common nfs-kernel-server

[apandrade]

This works for me on Ubuntu 18.10

sudo apt-get install nfs-common nfs-kernel-server

[dinhtuan242]

sudo apt-get install nfs-common nfs-kernel-server still working on Ubuntu 18.04 03/07/2019

[parvind87]

sudo apt-get install nfs-common nfs-kernel-server still working on Ubuntu 18.04 24 Oct 2019

[LOMFM]

Above command works for me ( on Ubuntu 18.04 ).
sudo apt-get install nfs-common nfs-kernel-server
Thanks all.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.