/vagrant is created inside your VM when vagrant is able to connect via ssh and the proper kernel modules are loaded to allow it to map a folder in. This requires VMware Tools or Virtualbox Extensions in order to function, so unless you changed the shared folder type to smb or nfs or rsync and have set up those binaries, you need to make sure your original box has the tools/extensions installed.
On Wednesday, October 7, 2015 at 2:23:07 AM UTC-5, Mwaniki Nderi wrote: > > I am a new to Vagrant and I do not seem to get anything started. I have > spent a week trying to set it up but I am having difficulties. > > I cannot access /Vagrant when I do ls /vagrant or even cd /vagrant and yet > when I pwd, I get /home/vagrant > > I am using git and I can successfully vagrant ssh > > What could be wrong. Thanks > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/aacb806a-cf38-4c8f-98a1-06e97e33dda7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
