Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NFS synced folders do not survive a reboot #1587

Closed
jcsp opened this issue Apr 12, 2013 · 2 comments
Closed

NFS synced folders do not survive a reboot #1587

jcsp opened this issue Apr 12, 2013 · 2 comments

Comments

@jcsp
Copy link

jcsp commented Apr 12, 2013

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.

@mattmcmanus
Copy link

+1 for this w/ Virtualbox as well.

(Vagrant 1.1.5 & Virtual Box 4.2)

Maybe the automount option should be enabled when you create the shares?

automount

@mitchellh
Copy link
Contributor

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants