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

Error on installing bindfs plugin #8030

Closed
janw-me opened this issue Nov 21, 2016 · 3 comments
Closed

Error on installing bindfs plugin #8030

janw-me opened this issue Nov 21, 2016 · 3 comments

Comments

@janw-me
Copy link

janw-me commented Nov 21, 2016

When I try to install vagrant-bindfs I get an error, see below.
I did manage to install vagrant-hostsupdater

Vagrant version

Vagrant 1.8.7
ruby 2.3.1p112 (2016-04-26) [x86_64-linux-gnu] (installed by vagrant)

Host operating system

Ubuntu Mate fully updated

Debug output

https://gist.github.com/janw-oostendorp/31c131631e9021eab346fca1039d788b

Expected behavior

Installing a plugin

Actual behavior

An error:

Installing the 'vagrant-bindfs' plugin. This can take a few minutes...
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 vagrant-bindfs (0.4.12), and Bundler cannot continue.
Make sure that `gem install vagrant-bindfs -v '0.4.12'` succeeds before bundling.

Warning: this Gemfile contains multiple primary sources. Using `source` more than once without a block is a security risk, and may result in installing unexpected gems. To resolve this warning, use a block to indicate which gems should come from the secondary source. To upgrade this warning to an error, run `bundle config disable_multisource true`.Gem::InstallError: vagrant-bindfs requires Ruby version ~> 2.0.0.

Steps to reproduce

  1. ~$ vagrant plugin install vagrant-bindfs
  2. get error
@jhaakma
Copy link

jhaakma commented Nov 22, 2016

I'm having the same issue. Looks like someone made a change to vagrant-bindfs which broke it:
gael-ian/vagrant-bindfs@58de1ab?_pjax=%23js-repo-pjax-container

Correction, that commit fixes the issue, but hasn't been pushed yet. For now try
vagrant plugin install vagrant-bindfs --plugin-version '0.4.11'

@janw-me
Copy link
Author

janw-me commented Nov 22, 2016

@jhaakma thanks that worked

@janw-me janw-me closed this as completed Nov 22, 2016
@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

2 participants