-
Notifications
You must be signed in to change notification settings - Fork 148
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
Fix incorrectly named file for Windows support #229
Conversation
This is impacting us as well. @seth-reeser can this be merged and released? |
Can everyone please provide a snippet from their Vagrant files as to how you're defining your machines? Providing that you use the syntax below this is a non-issue:
|
Here's ours @seth-reeser
|
@BadgerOps, what version of Vagrant and vagrant-hostmanager are you running? |
@seth-reeser I'm happy to help test with anything too - just let me know what I can do to help :) |
@BadgerOps what should be happening is a hosts file be created in a |
Our Vagrantfile looks like this, roughly -
The error we're seeing is as follows:
|
What are the operating systems of your workstations and guest virtual machines in question? |
Hi seth - I'm re-testing now, |
Host is either Windows 10 or MacOS Sierra, guest is opentable/win-2012r2-standard-amd64-nocm |
ok @seth-reeser just re-tested with a fresh VM and the above Vagrant config:
and c:\tmp\hosts exists - but not hosts.default or hosts.#{machine.name} edit: re-ran 'vagrant up' with debug logging turned on, and I see the following:
|
Ah, looks like maybe this line ?I'm not that familiar with ruby, but could it simply be missing a trailing / ? |
Aha! got it solved @seth-reeser,
the solution was to modify the following lines:
I've submitted a PR with this change here unless @pearcec wants to update this one. Thanks! |
#228
#228