Possible fix for not being able to run vagrant up under OSX #766
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
|
#765 for discussion. |
empeje
approved these changes
May 8, 2017
There was a problem hiding this comment.
Things I've reviewed:
- Check for issue number in pull request title
- Are there any unneeded files in the pull request?
- Did they make a branch for their patch?
- Does the pull request actually fix the issue?
- Check the pull request on rawgit, does it display without any errors?
- Is there any merge conflicts?
- Check the committer name?
Notes:
- Basically I agree with the changes, but I don't know much about installing on Mac, others please review about this.
- I also wonder, which one better to put this kind of troubleshooting solution, in FAQ or directly on the instruction page. Any suggestion?
dogi
approved these changes
May 9, 2017
empeje
suggested changes
May 9, 2017
pages/vagrant.md
Outdated
| ## Troubleshooting | ||
| When typing the command "vagrant up" in OSX, you may experience an error such as the following: "vi: Box 'ole/jessie64' could not be found. Attempting to find and install...". A simple solution is to perform the command below. ```sudo rm /opt/vagrant/embedded/bin/curl``` This will remove the old version of curl and vagrant should now work as usual. | ||
|
|
||
| For more information go here: (http://stackoverflow.com/questions/23874260/error-when-trying-vagrant-up) |
There was a problem hiding this comment.
Better to create a markdown link for the StackOverflow discussion.
Example: [Caption](URL)
There was a problem hiding this comment.
Thanks for the suggestions. I have added the proper markdown URL and also fixed the header formatting.
empeje
approved these changes
May 10, 2017
There was a problem hiding this comment.
Things I've reviewed:
- Check for issue number in pull request title
- Are there any unneeded files in the pull request?
- Did they make a branch for their patch?
- Does the pull request actually fix the issue?
- Check the pull request on rawgit, does it display without any errors?
- Is there any merge conflicts?
- Check the committer name?
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.
Added a suggestion for users experiencing the error "vi: Box 'ole/jessie64' could not be found. Attempting to find and install...". If the answer is on the page somewhere, users may less likely be deterred from installing Vagrant, saving the user time. I put all of this under a troubleshooting section near the end of document.
Update by @mappuji :
Rawgit here