10

I am trying to get homestead to work after following the instructions here

I have Virtualbox 5.0.6 and Vagrant 1.7.4 on windows 8. The machine boots up fine(ish) the only problem is that my mapped folder is not present on the vm, meaning when I vagrant ssh, the directory /home/vagrant/ is empty, there is no Code directory inside of it. This is a screenshot of the machine booting(it should keep going and saying mapping the folders and stuff):

machine booting

And this is the content of my Homestead.yaml file

---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox

authorize: C:\Users\Khalid\.ssh\id_rsa.pub

keys:
    - C:\Users\Khalid\.ssh\id_rsa

folders:
    - map: D:\work
      to: /home/vagrant/Code

sites:
    - map: homestead.app
      to: /home/vagrant/Code/Laravel/public

databases:
    - homestead

variables:
    - key: APP_ENV
      value: local

# blackfire:
#     - id: foo
#       token: bar
#       client-id: foo
#       client-token: bar

# ports:
#     - send: 93000
#       to: 9300
#     - send: 7777
#       to: 777
#       protocol: udp

Could someone please help, Thanks

EDIT: The full output of vagrant up --debug can be found here

Khalid Dabjan
  • 2,697
  • 2
  • 24
  • 35
  • Its weird you should have on start-up something that says `default: Mounting shared folders...` can you open Virtual Box, in the settings of you VM, check the sharing folder, see if you have something if you dont try to add a sharing folder and see if it works or if you have an error - last run `vagrant up --debug` and copy the full log somewhere on pastebin or gist – Frederic Henri Oct 16 '15 at 16:55
  • @FrédéricHenri After checking the shared folders in Virtual box I found my folder there `D:/work` . the question is updated with the full output of `vagrant up --debug` – Khalid Dabjan Oct 17 '15 at 12:18
  • What happens if you add double quotes around `D:\work`? – Jamesking56 Oct 17 '15 at 17:58
  • weird ... so the virtual box sees it ? what is it mapped to ? can you try replace `/home/vagrant/Code` with `/code` for example and see if you can access `/code` folder from the VM ? – Frederic Henri Oct 17 '15 at 20:00
  • What is the location of the homestead.yaml file you edited? – Nicklas Kevin Frank Oct 19 '15 at 12:52
  • @NicklasKevinFrank The file location is `C:\Users\Khalid\.homestead\Homestead.yaml` – Khalid Dabjan Oct 19 '15 at 14:03
  • None of the suggestions worked :( It feels like the stone age working with WAMP here. – Khalid Dabjan Oct 19 '15 at 14:06
  • What does `mount` command say, and did you check the system logs for any clues: `/var/log/syslog`. You'll need to connect to the virtual machine first: `homestead ssh` – madpoet Oct 23 '15 at 08:34

3 Answers3

12

sstarlight was on the right track. It's a path name issue. I'm on windows 8 with homestead too and you need to use the forward slashes even in your windows paths.

The below should do the trick!

authorize: C:/Users/Khalid/.ssh/id_rsa.pub

keys:
    - C:/Users/Khalid/.ssh/id_rsa

folders:
    - map: D:/work
      to: /home/vagrant/Code

sites:
    - map: homestead.app
      to: /home/vagrant/Code/Laravel/public

I would add to this that you should run the provisioning as per the other answer after you make the change by bringing your homestead up with the --provision flag set.

ShaunUK
  • 929
  • 6
  • 17
1

Make sure and re-verify that the path for the keys and authorize are correct and run vagrant up --provision to re-provision the homestead setup again

Abishek
  • 11,191
  • 19
  • 72
  • 111
0

Try change

 D:\work to D:/work/
ssuhat
  • 7,387
  • 18
  • 61
  • 116