When calling vagrant box add hashicorp/precise64, the box is not fetched from the server.
Seems to be related to embedded curl:
DEBUG subprocess: stderr: dyld: Library not loaded: @rpath/libcurl.4.dylib
Referenced from: /opt/vagrant/embedded/bin/curl
Reason: Incompatible library version: curl requires version 9.0.0 or later, but libcurl.4.dylib provides version 7.0.0
Jenss-MBP:kubernetes jenskanschik$ vagrant -v
Vagrant 1.8.7
MacOS Sierra, 10.12.1
Not possible.
Not relevant.
https://gist.github.com/jkanschik/fb6ee980993b36367141916704a490e2
vagrant box add hashicorp/precise64 should download the box.
Box could'nt be found.
vagrant box add hashicorp/precise64This is a duplicate of: GH-8012 and GH-7997
Jenss-MBP:kubernetes jenskanschik$ curl --version
curl 7.49.1 (x86_64-apple-darwin16.0) libcurl/7.49.1 SecureTransport zlib/1.2.8
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz UnixSockets
Jenss-MBP:kubernetes jenskanschik$
I've solved this. Please see here
Thanks @X0o0Z, you're my hero. sudo ln -nsf /usr/bin/curl /opt/vagrant/embedded/bin/curl did the trick. Great write up.
The same bug actual for ElCapitan
Hi, guys!
We are still trying to use vagrant to unify our developer environment. At first we thought "what could be easier than running virtual machine with ansible provision and getting exactly the same environment". But how wrong we were..
Every release there is some critical bug in very-very common stuff. Last time it was with auth to new box at default ssh config (default config!!). It took you a couple months to make new build of vagrant with fix. (fix was done in couple days, the rest of the time you seem to be waiting for something)
This time even more common stuff is broken - downloading boxes on newest macOS
Do you run any tests or may be just test new releases?
Maybe you need some help to build basic CI environment?
@maxgorovenko Not sure if being sarcastic will help here. This is a free (and open) tool.
I'm totally suffering the same, but complaining like this won't help.
That's also a project life: bugs can appear.
You can freely propose a Pull Request that implements a set of functionnal tests or corrects this bug with a unit test case :)
Confirmed http://pastie.org/10968105
Also mentioned in this closed issue: https://github.com/mitchellh/vagrant/issues/5016#issuecomment-260065012
duplicate of https://github.com/mitchellh/vagrant/issues/7969
I'm going to lock this issue because it has been closed for _30 days_ โณ. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Most helpful comment
Hi, guys!
We are still trying to use vagrant to unify our developer environment. At first we thought "what could be easier than running virtual machine with ansible provision and getting exactly the same environment". But how wrong we were..
Every release there is some critical bug in very-very common stuff. Last time it was with auth to new box at default ssh config (default config!!). It took you a couple months to make new build of vagrant with fix. (fix was done in couple days, the rest of the time you seem to be waiting for something)
This time even more common stuff is broken - downloading boxes on newest macOS
Do you run any tests or may be just test new releases?
Maybe you need some help to build basic CI environment?