Default hostname using FQDN make vagrant fail with windows guest #117
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
Since vagrant 1.6.4 vagrant fails to setup windows guest with FQDN as hostname.
sethvargo
added a commit
that referenced
this pull request
Nov 10, 2014
Default hostname using FQDN make vagrant fail with windows guest
|
Thanks! |
|
@Annih As I'm reviewing changes for a release of this Driver, I thought I'd drop a note to say that I'm handling |
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.
Since vagrant 1.6.4 vagrant fails to setup windows guest with FQDN as hostname because it exceed the 15 characters limit.
Even some Linux systems do not recommend to use FQDN as hostname.
If needed, I can add a test on the "guest" property to use FQDN on all guest which are not windows.