Closed riebling closed 7 years ago
And that comment led me to a solution, should anyone else receive these errors! The fix:
sudo rm -rf /var/lib/gems
Now this plugin can install happily. (who knew?)
er1k@islpc22:~/boxes/xenial-AWS/dummy$ vagrant plugin install vagrant-sshfs
Installing the 'vagrant-sshfs' plugin. This can take a few minutes...
Installed the plugin 'vagrant-sshfs (1.3.0)'!
Nope. Doesn't help. Tried installing the wrong plugin, vagrant-sshfs, which installed OK. vagrant-aws still heaps piles of gripes about gems on us.
Trying suggested commands to determine source of problem leads to advice to run gem install fog-xml
, the results:
er1k@islpc22:~/boxes/xenial-AWS/dummy$ sudo gem install fog-xml
Fetching: builder-3.2.2.gem (100%)
Fetching: excon-0.54.0.gem (100%)
Fetching: formatador-0.2.5.gem (100%)
Fetching: fog-core-1.43.0.gem (100%)
Fetching: mini_portile2-2.1.0.gem (100%)
ERROR: Error installing fog-xml:
mini_portile2 requires Ruby version >= 1.9.2.
Fixed it after realizing it was due to misleading error message. Here is how the error message reads:
This is usually caused by manual tampering with the 'plugins.json'
file in the Vagrant home directory. To fix this error, please
remove that file
Here is how it should read
This is usually caused by manual tampering with the 'plugins.json'
file in the ~/.vagrant.d directory. To fix this error, please
remove that file
because there is also a plugins.json to be found in /opt/vagrant, which one might assume is Vagrant's home directory, but one would be wrong. "the Vagrant home directory" is imprecise, ambiguous, and misleading
wget -c https://releases.hashicorp.com/vagrant/2.0.3/vagrant_2.0.3_x86_64.deb sudo dpkg -i vagrant_2.0.3_x86_64.deb
OS: Ubuntu 12.04 Vagrant version: vagrant_1.9.0_x86_64.deb Try
vagrant plugin install vagrant-aws
The same happens even if I (tried to) remove all traces of Ruby from my system (because I suspected a failed Ruby install may have been the initial cause of this behavior) - I'm really not sure how Vagrant's dependency on Ruby is meant to work, or "just work" or, in this case, "not work" :-/