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 Issue #114

Closed
ajkim opened this issue Aug 21, 2014 · 1 comment
Closed

Vagrant Issue #114

ajkim opened this issue Aug 21, 2014 · 1 comment

Comments

@ajkim
Copy link

ajkim commented Aug 21, 2014

Trying to install your host manager with following command:
----> vagrant plugin install vagrant-hostmanager
(Have also tried this with sudo)

Error output consistently remarks:
"Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

An error occurred while installing nokogiri (1.6.3.1), and Bundler cannot continue.
Make sure that gem install nokogiri -v '1.6.3.1' succeeds before bundling."

At this point, Nokogiri is absolutely installed in my comp.

Have tried workarounds found on Google:
ARCHFLAGS=-Wno-error=unused-command-line-argument-hard-error-in-future gem install nokogiri -v '1.6.3.1' -- --with-iconv-include=/usr/local/opt/libiconv/include --with-iconv-lib=/usr/local/opt/libiconv/include

and

ARCHFLAGS=-Wno-error=unused-command-line-argument-hard-error-in-future vagrant plugin install vagrant-hostmanager

None of these methods have worked at all and now at a roadblock.

Any ideas on how to fix this issue?

@pbitty
Copy link
Contributor

pbitty commented Aug 26, 2014

Hi @ajkim, this seems to be a known issue with vagrant itself and how it deals with dependencies when installing plugins (ie: vagrant-hostmanager doesn't even depend on nokogiri, but vagrant still tries to install it).

Anyway, there is a long thread in hashicorp/vagrant#3769 about this. Take a look at this comment, which may be a usable work-around. I haven't run into the issue myself, and haven't found a way to reproduce it.

Also, the instruction to run gem install nokogiri... is a bit misleading, because vagrant has its own copy of Ruby, with its own gems folder and so on. When you run gem install nokogiri, it installs nokogiri in your "system" copy of Ruby and not in vagrant's Ruby - so vagrant still won't see that version of nokogiri.

I hope this helps. I am closing this for now. If you are having trouble and would like to discuss more, feel free to reopen it.

@pbitty pbitty closed this as completed Aug 26, 2014
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

2 participants