Fix for windows users with wrong host_ip #58
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Users on windows has reported that they cannot get vagrant up and running because of a bug in Vagrant not being able to use the default `0.0.0.0`-ip for localhost. By using `127.0.0.1` instead, this works out ok.
|
The bug in question is located here: hashicorp/vagrant#8395 There is a fix for it, but might be worth including this patch for users on that version. |
|
Thanks for doing this! I'll test it on the Mac and will merge it assuming that goes well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Users on windows has reported that they cannot get vagrant up and running because of a bug in Vagrant not being able to use the default
0.0.0.0-ip for localhost. By using127.0.0.1instead, this works out ok.