From e003b45f9cbc4a12eba7fe4ecb769e499f185f60 Mon Sep 17 00:00:00 2001 From: Mitchell Hashimoto Date: Mon, 6 Jul 2015 23:19:18 -0600 Subject: [PATCH] website: update docs about NFS encryption [GH-4987] --- website/docs/source/v2/synced-folders/nfs.html.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/website/docs/source/v2/synced-folders/nfs.html.md b/website/docs/source/v2/synced-folders/nfs.html.md index b11acb453..3468edd0d 100644 --- a/website/docs/source/v2/synced-folders/nfs.html.md +++ b/website/docs/source/v2/synced-folders/nfs.html.md @@ -78,7 +78,7 @@ config.vm.synced_folder ".", "/vagrant", ``` This would result in the following `mount` command being executed on the guest: - + ``` mount -o 'actimeo=2' 172.28.128.1:'/path/to/vagrantfile' /vagrant ``` @@ -151,3 +151,11 @@ Cmnd_Alias VAGRANT_NFSD_APPLY = /usr/sbin/exportfs -ar Cmnd_Alias VAGRANT_EXPORTS_REMOVE = /bin/sed -r -e * d -ibak /etc/exports %vagrant ALL=(root) NOPASSWD: VAGRANT_EXPORTS_ADD, VAGRANT_NFSD_CHECK, VAGRANT_NFSD_START, VAGRANT_NFSD_APPLY, VAGRANT_EXPORTS_REMOVE ``` + +## Other Notes + +**Encrypted folders:** If you have an encrypted disk, then NFS very often +will refuse to export the filesystem. The error message given by NFS is +often not clear. One error message seen is ` does not support NFS`. +There is no workaround for this other than sharing a directory which isn't +encrypted.