Closed wizonesolutions closed 4 years ago
@wizonesolutions Sorry for the super-late response :).
The provider doesn't change any settings related to upstream synced folders (like NFS), so it goes directly to Vagrant. If the issue still actual - I would suggest to search Vagrant issues for that (https://github.com/hashicorp/vagrant/).
But first I would make sure that your Vagrantfile
actually has nfs_export
option set to false explicitly. Your snipped doesn't have it, so it seems Vagrant treats is as true by default.
The option itself should work fine, as people say: https://github.com/hashicorp/vagrant/issues/11209#issuecomment-557102899
Vagrant allows this if we don't want the
/etc/exports
file edited: https://www.vagrantup.com/docs/synced-folders/nfs.html#nfs-synced-folder-optionsHowever, Vagrant Parallels either doesn't pass this option on or doesn't implement it (I'm not clear who's responsible for this actual edit).
Here's some
info
-level logging that I was using to check if the setting was actually set:The relevant Vagrantfile snippet (it's from geerlingguy/drupalvm) looks like:
I have confirmed that
nfs_export
is actually getting set to Rubyfalse
.The logs above suggest that the
nfs_export
option isn't visible to Vagrant when it's deciding whether to edit/etc/exports
or not, but that doesn't really make any sense given how the Vagrantfile works...