Updates documentation to respect Vagrantfile case sensitivity on strict file systems #4939
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
|
Unsure why this build failed, seems like there was already an address in use, possible Travis issue in the build setup. |
sethvargo
added a commit
that referenced
this pull request
Dec 11, 2014
Updates documentation to respect Vagrantfile case sensitivity on strict file systems
|
Thanks! |
ghost
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This is a fix for issue #4907. On strict case sensitive filesystems, the Vagrantfile must follow that exact casing, otherwise Vagrant will fail to launch and will complain no Vagrantfile exists.
This change adds further accuracy to the documentation to prevent people stumbling into a trap on such file systems.
cc/ @mitchellh @sethvargo