-
Notifications
You must be signed in to change notification settings - Fork 38
Unable to find the file '/provision/main/etc/hosts.json' #5
Comments
Same thing here:
|
Could you please post the full console output so that I can figure out what causes the issue |
The issue is caused by there being no '/provision/main/etc/hosts.json'. On Wednesday, March 4, 2015, Mohamed Kholy notifications@github.com wrote:
Thanks! |
The file '/provision/main/etc/hosts.json' is not included with the repository, instead it is automatically generated during the provisioning process. |
Thanks very much! It's fixed. |
Windows 7. Vagrant 1.7.2. VirtualBox 4.3.18. |
Could you please post the full console output? it will help me better identify your issue. |
|
The problem is in this line:
This is caused by an issue in your Git line ending configuration, it converts the line ending of the file Please check the value of this |
It's set to false. Same issue. |
Did git convert the line endings when I cloned the repo? Should I re-clone now that I changed the value? |
I have just added a |
Worked perfectly! Thanks very much. |
Actually, something else happened. It ran OK and I managed to go to http://dashbrew.dev/ but it was accesible for 5 seconds. Using the sample environment config I get this output when
|
Ok, try destroying your vagrant machine by running |
Basically, the same thing. It's not even picking up the env config:
|
Here's some more. I went to my hosts file and removed what I had from before. Ran
This is how the hosts file looks:
After
|
Don't know if this is relevant but, did
|
More madness. Used Definitely problems with line endings :( |
I am not sure why all of this is happening. |
Kill the dos line endings with sed -i 's/\r//' /vagrant/provision/main/dashbew works for all you guys struggling on windows 7. |
I saw this project on Reddit, so I thought I'd check it out. However, I'm missing the file '/provision/main/etc/hosts.json', so I have to edit the host files on both machines myself. There's nothing in the wiki, so I can't look up any documentation on the matter. Can you include the file in the repo?
The text was updated successfully, but these errors were encountered: