haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

website/docs: document need for private network for NFS

This commit is contained in:
Mitchell Hashimoto 2013-11-23 14:07:46 -08:00
parent 97389d4255
commit 8a0f209f3f
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/docs/source/v2/synced-folders/nfs.html.md
View File

@ -28,6 +28,11 @@ OS X, and is typically a simple package install on Linux.
Additionally, the guest machine must have NFS support installed. This is
also usually a simple package installation away.
If you're using the VirtualBox provider, you'll also need to make sure you
have a
[private network setup with a static IP](http://localhost:4567/v2/networking/private_network.html). This is due to a limitation of VirtualBox's built-in networking. With
VMware, you do not need this.
## Root Privilege Requirement
To configure NFS, Vagrant must modify system files on the host. Therefore,
@ -36,7 +41,6 @@ administrative privileges (via the typical `sudo` program). These
privileges are used to modify `/etc/exports` as well as to start and
stop the NFS server daemon.
## Enabling NFS Synced Folders
To enable NFS, just add the `type: "nfs"` flag onto your synced folder: