You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NFS synced folders appear to be configured ephemerally, so that if the VM reboots itself (e.g. after installing a new kernel) then the synced folder is lost.
NFS shares should be configured persistently within the VM, or at least this limitation of the option NFS should be mentioned in the docs.
The text was updated successfully, but these errors were encountered:
Vagrant doesn't modify your '/etc/fstab', so if you reboot the VM it is up to you to remount it. Vagrant includes reload for this reason, if you run reload it will gracefully reboot and remount folders.
There has been some talk about adding a plumbing method to just mount folders. But for the time being, this is annoyingly "working as intended". But use reload if you need it remounted.
Vagrant 1.1.5 + vmware_fusion provider
NFS synced folders appear to be configured ephemerally, so that if the VM reboots itself (e.g. after installing a new kernel) then the synced folder is lost.
NFS shares should be configured persistently within the VM, or at least this limitation of the option NFS should be mentioned in the docs.
The text was updated successfully, but these errors were encountered: