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

Vagrant Virtualbox NFS / mounting issues #66

Closed
enapthine opened this Issue Apr 6, 2015 · 8 comments

Comments

4 participants
@enapthine
Copy link

enapthine commented Apr 6, 2015

Ran into issues when mounting shares (NFS & not), eventually discovered was caused by differing VirtualboxGuestAdditions that wasn't being detected. Not specifically DrupalVM related, but worth documenting. This could be related to earlier bug report regarding NFS shares also, as it stalls at the same location.

Resolved with installing vbguest plugin via:

vagrant plugin install vagrant-vbguest

@stefanruijsenaars

This comment has been minimized.

Copy link

stefanruijsenaars commented Apr 6, 2015

I think I may have mount related issues as well, I am running into this issue: https://www.drupal.org/node/2234229

I wonder if replacing NFS with this could help? http://wolfgangziegler.net/auto-rsync-local-changes-to-remote-server#comments

@geerlingguy

This comment has been minimized.

Copy link
Owner

geerlingguy commented Apr 6, 2015

@stefanruijsenaars - I've hit that issue as well, but not with Drupal VM: https://www.drupal.org/node/2234229#comment-9744087

You can always switch to rsync if you would rather try that sync method, but with the out-of-the-box configuration, the Drupal install will be written over if you put files into your local folder that's synced inside the VM.

To use rsync, just set the type of the synced folder to rsync. I'm hoping Vagrant will someday add two-way rsync out of the box, though!

@enapthine - I think I may add a Wiki page with NFS common problems and fixes; enough people have trouble with shared folders of all varieties, and simply keeping my VirtualBox boxes up to date isn't enough all the time (I hate how VirtualBox seems to cause problems every other version upgrade!)

@geerlingguy geerlingguy added the question label Apr 6, 2015

@stefanruijsenaars

This comment has been minimized.

Copy link

stefanruijsenaars commented Apr 6, 2015

@geerlingguy I think the solution in the link actually bypasses Vagrant synced folders completely, it's a script by fago that watches a directory for changes using inotify-tools and rsyncs the changes to a remote system via SSH.

@stefanruijsenaars

This comment has been minimized.

Copy link

stefanruijsenaars commented Apr 6, 2015

I reckon this is some kind of problem with permissions on the NFS share, now I had a Simpletest fail because it couldn't create a directory :)

@stefanruijsenaars

This comment has been minimized.

Copy link

stefanruijsenaars commented Apr 6, 2015

Which I fixed by adding the following to the synced folders section in the Vagrantfile:

owner: "vagrant",
group: "www-data",
mount_options: ["dmode=775,fmode=664"]
@geerlingguy

This comment has been minimized.

Copy link
Owner

geerlingguy commented Apr 23, 2015

I think I may just set up a Wiki page discussing NFS and Synced Folder troubleshooting, and we can work on adding relevant examples/fixes in there. It seems like half or more of the issues reported so far on this project have to do with synced folders.

Hopefully, someday, Vagrant will support out-of-the-box two-way rsync!

@geerlingguy

This comment has been minimized.

geerlingguy added a commit that referenced this issue Apr 23, 2015

geerlingguy added a commit that referenced this issue Apr 23, 2015

@iainhouston

This comment has been minimized.

Copy link
Contributor

iainhouston commented Feb 13, 2016

It seems that root can write to the sync'd folders but vagrant can't. Is that the intended behaviour?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment