-
Notifications
You must be signed in to change notification settings - Fork 397
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
When using VM built with vm:init, NFS synced folder doesn't always mount correctly #214
Comments
Note that some developers have reported that simply reverting to Vagrant 1.8.1 resolves the issue; this could be related to hashicorp/vagrant#7443 (PR with fix here: hashicorp/vagrant#7492). |
Wonder if this is somehow related to #241 Edit: I'm an idiot and this has already been merged. :) |
@geerlingguy Reading geerlingguy/drupal-vm#783 suggests to me that this is not a BLT issue. Closing issue here--workarounds documented in geerlingguy/drupal-vm#783 |
Yep! |
Steps to Reproduce
vm:init
vagrant up
the new Drupal VMvagrant ssh
into the VMcd
into the synced folder dir (e.g./var/www/[project]
) and runls
Expected Results
sudo mount
inside VM returns a result like172.16.101.1:/Users/geerlingguy/Desktop/project on /var/www/project type nfs (rw,vers=3,udp,addr=172.16.101.1)
Actual Results
sudo mount
inside VM doesn't return a mount for the/var/www/[project]
folder.I'm digging deeper into this now, and making sure it's not something that's fixed/working in BLT master vs. a slightly older version that might've had a problem with the default config.
The text was updated successfully, but these errors were encountered: