contents of /vagrant folder on guest not syncing with /[project] folder on host

[Jeff Widman]

New to Vagrant and having an issue, as I walk through the Getting Started guide. 

The sync'd folders aren't working by default:

vagrant up

vagrant ssh

"pwd" says /vagrant

touch foo

exit 

 

Back on host machine, the project directory where the vagrant file resides shows no sign of foo. searching the rest of my computer also shows no sign of foo.

I've reinstalled VirtualBox and Vagrant, and neither one fixed the issue. I'm on OSX Mountain Lion. The only change I made from the Getting Started guide was I used the precise64 box instead of the precise32.

Any suggestions for how to better pinpoint the underlying issue and fix it? 

Cheers,

Jeff

[Terrance Shepherd]

What version of virtual box are you using?

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Jeff Widman]

Actually, looking at this a little more, it looks like the guest additions included with the precise64 box are now outdated, that would explain it. Guest Additions are 4.2.0 vs Virtualbox is currently on 4.3.4

I just checked, and the precise32 image also uses Guest Additions 4.2.0 and also has the same issue with files not being shared between /vagrant and /[project]

Since this is the recommended box to download, I added a ticket on github to update the base box, so that n00bs like myself can hit the ground running.

[Teemu Matilainen]

Hi Jeff,

Please gist your Vagrantfile and debug output of vagrant up.

-- 

Teemu

--

[Jeff Widman]

Here you go Teemu:

https://gist.github.com/jeffwidman/c9e145a70bae2dd5c8ba

As I mentioned, I suspect it's an issue with latest Virtualbox being 4.3.4 and guest additions packaged in the precise32 box being Vbox 4.2.0

[Jeff Widman]

Just updated guest additions to match the host virtualbox version, but the problem persists--/vagrant on guest and /[project] on host are not syncing.

The guest additions were updated by installing the vagrant-vbguest plugin (thanks for pointing me toward that Teemu).

Here's an updated gist with the new log output using the "debug" option: https://gist.github.com/jeffwidman/3549a6f07ec8768dac15

--
You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/cSqm9qHtBDM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--

Jeff Widman

740-WIDMAN-J (943-6265)

http://www.jeffwidman.com/

<><

[Teemu Matilainen]

Jeff,

I don't see anything strange in that log. One thing that you could try is to restart the VM with `vagrant reload` (same as `vagrant halt; vagrant up`). Maybe the new drivers didn't kick in correctly (in which case it's a vagrant-vbguest issue as it should have restarted the VM).

-- 

Teemu

[Jeff Widman]

Nope--I figured it out. 

I didn't realize I should be looking at "/vagrant" rather than "/home/vagrant"

after "vagrant up", I hit "pwd" and got "/home/vagrant" and assumed that was the "/vagrant" mentioned in the docs. My mistake.

[Alex Grushevsky]

This is outrageous, the official tutorial leads directly into this trap! How can that  possibly be? Just did https://www.vagrantup.com/docs/getting-started/synced_folders.html and run into same issue, was not able to solve until found this post.

>after "vagrant up", I hit "pwd" and got "/home/vagrant" and assumed that was the "/vagrant" mentioned in the docs. My mistake.

Not your, it is their mistake.

воскресенье, 15 декабря 2013 г., 6:46:10 UTC+7 пользователь Jeff Widman написал:

[Alvaro Miranda Aguilera]

Hello.

If you can share with me where do you think this can benefit from some clarification, we can review and put a note if that helps .

Alvaro.

This email has been sent from a virus-free computer protected by Avast. www.avast.com

On Fri, Jan 29, 2016 at 8:41 PM, Alex Grushevsky <alex.gr...@gmail.com> wrote:

This is outrageous, the official tutorial leads directly into this trap! How can that  possibly be? Just did https://www.vagrantup.com/docs/getting-started/synced_folders.html and run into same issue, was not able to solve until found this post.

>after "vagrant up", I hit "pwd" and got "/home/vagrant" and assumed that was the "/vagrant" mentioned in the docs. My mistake.

Not your, it is their mistake.

воскресенье, 15 декабря 2013 г., 6:46:10 UTC+7 пользователь Jeff Widman написал:

Nope--I figured it out. 

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---

You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/9ea5281c-a72a-49ee-acc0-694a6b35ba03%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Lekhnath Rijal]

I did the same mistake and after hours of googling I found this thread and you saved me :) Thanks for mentioning .