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 box add fails in version 1.8.7, succeeds in 1.8.1 #7993

Closed
romski opened this issue Nov 11, 2016 · 6 comments
Closed

Vagrant box add fails in version 1.8.7, succeeds in 1.8.1 #7993

romski opened this issue Nov 11, 2016 · 6 comments

Comments

@romski
Copy link

romski commented Nov 11, 2016

Please note that the Vagrant issue tracker is reserved for bug reports and
enhancements. For general usage questions, please use the Vagrant mailing list:
https://groups.google.com/forum/#!forum/vagrant-up. Thank you!

Vagrant version

1.8.7

Host operating system

OS X 10.11.6

Guest operating system

Ubuntu 14.04 64bit

Vagrantfile

n/a

Debug output

See comments below

Expected behavior

Box should be added

Actual behavior

Error:
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'mybox' (v0) for provider:
box: Unpacking necessary files from: file:///mybox.box
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

Steps to reproduce

I am using a private box created using Vagrant 1.8.1

  1. Install vagrant 1.8.7
  2. Add box

References

n/a

@andreabedini
Copy link

I seem to have the same problem. Here is the relevant part of the debug log

 INFO subprocess: Command in the installer. Specifying DYLD_LIBRARY_PATH...
DEBUG subprocess: Selecting on IO
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
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 6
 WARN downloader: Downloader exit code: 6
ERROR downloader: Exit code: 6

indeed

$ DYLD_LIBRARY_PATH=/opt/vagrant/embedded/lib/ /opt/vagrant/embedded/bin/curl
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
zsh: abort      /opt/vagrant/embedded/bin/curl
$ otool -L   /opt/vagrant/embedded/bin/curl
/opt/vagrant/embedded/bin/curl:
    @rpath/libcurl.4.dylib (compatibility version 9.0.0, current version 9.0.0)
    @rpath/libssh2.1.dylib (compatibility version 2.0.0, current version 2.1.0)
    @rpath/libssl.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
    @rpath/libcrypto.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
    @rpath/libz.1.dylib (compatibility version 1.0.0, current version 1.2.8)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1197.1.1)
    /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 2577.0.0)

Admittedly, I never really understood rpaths 😞

@andreabedini
Copy link

This has been already noticed in https://groups.google.com/forum/#!topic/vagrant-up/RdC6AXRWjQE

@romski
Copy link
Author

romski commented Nov 11, 2016

@andreabedini Thanks for adding the debug/links. I'd already uninstalled and didnt have time to go back for the debug when raising the issue. This has saved me the job :)

@garystafford
Copy link

I had the exact same issue and debug results on OS X 10.11.6 as described above with v1.8.7, running any vagrant up or vagrant box add command (i.e. vagrant box add hashicorp/precise64). I downgraded to Vagrant v1.8.6 from v1.8.7. I was then successful in adding the box (box: Successfully added box 'hashicorp/precise64' (v1.1.0) for 'virtualbox'!). The issue seems to be specific to v1.8.7 on Mac?

@chrisroberts
Copy link
Member

Dup of #7969. Thanks for the report!

@ghost
Copy link

ghost commented Apr 3, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants