Skip to content
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

Vagrant up won't complete #315

Open
Brendans93 opened this issue Nov 15, 2016 · 2 comments
Open

Vagrant up won't complete #315

Brendans93 opened this issue Nov 15, 2016 · 2 comments

Comments

@Brendans93
Copy link

I've looked through past posts and can't find anything that is similar enough to my problem. I am running Mac OS X (El Capitan), Virtual Box 4.3.26 and Vagrant 1.8.7. I have cloned the necessary files and navigated to the top level of the folder with the Vagrantfile. When I type "vagrant up", the following is shown:

brendan (master) Mining-the-Social-Web-2nd-Edition $ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'precise64' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Box file was not detected as metadata. Adding it directly...
==> default: Adding box 'precise64' (v0) for provider: virtualbox
default: Downloading: http://files.vagrantup.com/precise64.box
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

There is no error message and I don't know how to proceed. I am familiar with setting up Virtual boxes for Linux systems, and I have not done anything of that sorts here. The video does not describe creating a new virtual machine. Do I need to make one?

Thanks

@pavlin99th
Copy link

This is an issue with vagrant 1.8.7 on OS X, see hashicorp/vagrant#7969 and hashicorp/vagrant#7970. curl utility shipped with this version of vagrant appears to be invalid.

The solution is sudo rm /opt/vagrant/embedded/bin/curl - this will remove curl bundled with vagrant and cause it to fall back to system's one at /usr/bin/curl.

@rreben
Copy link

rreben commented Nov 28, 2016

Or going back to vagrant 1.8.6 will also solve the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants