Closed fowlie closed 9 years ago
Hi Mats,
vagrant-proxyconf (nor Vagrant) doesn't depend on the json gem (which is only needed in Ruby 1.8, while Vagrant bundles 2.0), so it has to come from another plugin you have installed. Try uninstalling other plugins from vagrant plugin list
to find the one to blame. =)
That makes sense. The odd thing is that the only steps I did was to install VirtualBox, then Vagrant and that's it. I have done no configs/hacking, and haven't installed any other plugins. If I run vagrant plugin list
I get this:
C:\Users\webshop>vagrant plugin list vagrant-share (1.1.3, system)
Oh, that for sure is strange. vagrant-proxyconf doesn't have any dependencies, so I really don't understand where that json gem comes from...
But anyway, looking at the error message it seems that the issue might be the space in the installation path.
You're right, uninstalling and installing Vagrant again in a different path withouth the space solved the problem. Thanks a lot for helping out :smiley:
No prob, good you got it solved. But the json gem remains a mystery. =)
Hi, I've just installed Vagrant 1.7.2, and ran
vagrant plugin install vagrant-proxyconf
. I then got this error:I can't find any help with google, and this error message is very confusing for someone new to dem/bundler. Any help please?
Thanks