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

Wrong version of libcurl installed as part of vagrant 1.8.7 #8036

Closed
alantech21 opened this issue Nov 25, 2016 · 5 comments
Closed

Wrong version of libcurl installed as part of vagrant 1.8.7 #8036

alantech21 opened this issue Nov 25, 2016 · 5 comments

Comments

@alantech21
Copy link

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

Run vagrant -v to show the version. If you are not running the latest version
of Vagrant, please upgrade before submitting an issue.
1.8.7

Host operating system

This is the operating system that you run locally.
macOS 10.12.1

Guest operating system

This is the operating system you run in the virtual machine.
none yet.

Vagrantfile

# Copy-paste your Vagrantfile here

not applicable

Please note, if you are using Homestead or a different Vagrantfile format, we
may be unable to assist with your issue. Try to reproduce the issue using a
vanilla Vagrantfile first.

Debug output

Provide a link to a GitHub Gist containing the complete debug output:
https://www.vagrantup.com/docs/other/debugging.html. The debug output should
be very long. Do NOT paste the debug output in the issue, just paste the
link to the Gist.

Expected behavior

What should have happened?
vagrant command should have executed.

Actual behavior

What actually happened?
Error message returned, and Crash Reporter runs.
Error is as follows:
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
Abort trap: 6

Short version: vagrant does not work at all.

One possibility: if @rpath is not set, it could be trying to use the libcurl.4.dylib in /usr/lib, but that one is actually a newer version than the vagrant included version.

Steps to reproduce

  1. enter command 'vagrant' with or without any action or arguments

References

Are there any other GitHub issues (open or closed) that should be linked here?
For example:

@scottslowe
Copy link

scottslowe commented Nov 26, 2016

This issue is also affecting my OS X systems, which are running 10.11.6. Normal Vagrant usage doesn't return an error; it was only through some debugging that I found I was also affected.

The error message returned is:

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
Trace/BPT trap: 5

As a workaround, I symlinked OS X's version of curl in the /opt/vagrant/embedded/bin directory, and now things seem to work.

@leehus
Copy link

leehus commented Nov 28, 2016

I got same problem

INFO subprocess: Starting process: ["/opt/vagrant/embedded/bin/curl", "-q", "--fail", "--location", "--max-redirs", "10", "--user-agent", "Vagrant/1.8.7 (+https://www.vagrantup.com; ruby2.2.5)", "--continue-at", "-", "--output", "/Users/username/.vagrant.d/tmp/boxb7c2b1abb8b632b03ab2fd8887faea66ef659f68", "https://storage.googleapis.com/stable.release.core-os.net/amd64-usr/current/coreos_production_vagrant_vmware_fusion.json"] 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

os:10.12.1
vagrant 1.8.7
ruby:2.3.0

@leehus
Copy link

leehus commented Nov 28, 2016

#7969
it worked

@chrisroberts
Copy link
Member

Closing as dup of #7969

@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