I'm trying to install the vagrant-windows plugin on a windows 7 (64 bit) machine, but I get the error below. How can I fix this?
further info:
ruby version installed on machine 1.9.3
in corporate environment (port 80, 443, 3389 open)
Vagrant installed via chocolatey (version 1.3.5)
This is the stacktrace:
Installing the 'vagrant-windows' plugin. This can take a few minutes...
C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems.rb:566:in `inflate': incorrect header check (Zlib::DataError)
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems.rb:566:in `inflate'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:122:in `fetch_spec'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:95:in `block in fetch_with_errors'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:94:in `map'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:94:in `fetch_with_errors'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/dependency_installer.rb:110:in `find_gems_with_sources'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/dependency_installer.rb:174:in `block in add_found_dependencies'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/dependency_installer.rb:171:in `each'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/dependency_installer.rb:171:in `add_found_dependencies'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/dependency_installer.rb:142:in `gather_dependencies'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/dependency_installer.rb:267:in `install'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/plugin/action/install_gem.rb:49:in `block in call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/plugin/gem_helper.rb:42:in `block in with_environment'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/user_interaction.rb:40:in `use_ui'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/plugin/gem_helper.rb:41:in `with_environment'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/plugin/action/install_gem.rb:39:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/plugin/action/bundler_check.rb:20:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builder.rb:116:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `block in run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/util/busy.rb:19:in `busy'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/plugin/command/base.rb:17:in `action'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/plugin/command/install.rb:27:in `execute'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/plugin/command/root.rb:52:in `execute'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/cli.rb:38:in `execute'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/environment.rb:478:in `cli'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.3.5/bin/vagrant:96:in `<top (required)>'
from C:/HashiCorp/Vagrant/bin//../embedded/../embedded/gems/bin/vagrant:23:in `load'
from C:/HashiCorp/Vagrant/bin//../embedded/../embedded/gems/bin/vagrant:23:in `<main>'
I'm not entirely sure what the problem was.
The solution however was to disable all unused network adapters.
The issue is tracked here.
Related
My development environment relies on vagrant and virtual box. Everything used to work until a few days ago. Since then, every time I try to run vagrant up, I'm getting this error message.
I don't really know what to do about it. Any advice?
C:/Users/D3TzH/.vagrant.d/gems/2.4.4/gems/vagrant-triggers-0.5.3/lib/vagrant-triggers/dsl.rb:90:in `method_missing': undefined method `run_remote=' for #<VagrantPlugins::Triggers::DSL:0x00000000049cb5b8> (NoMethodError)
from D:/Projects/D3TzH/D3TzH-environment/Vagrantfile:41:in `block (2 levels) in <top (required)>'
from C:/Users/D3TzH/.vagrant.d/gems/2.4.4/gems/vagrant-triggers-0.5.3/lib/vagrant-triggers/dsl.rb:11:in `instance_eval'
from C:/Users/D3TzH/.vagrant.d/gems/2.4.4/gems/vagrant-triggers-0.5.3/lib/vagrant-triggers/dsl.rb:11:in `fire!'
from C:/Users/D3TzH/.vagrant.d/gems/2.4.4/gems/vagrant-triggers-0.5.3/lib/vagrant-triggers/action/trigger.rb:52:in `block in fire_triggers'
from C:/Users/D3TzH/.vagrant.d/gems/2.4.4/gems/vagrant-triggers-0.5.3/lib/vagrant-triggers/action/trigger.rb:51:in `each'
from C:/Users/D3TzH/.vagrant.d/gems/2.4.4/gems/vagrant-triggers-0.5.3/lib/vagrant-triggers/action/trigger.rb:51:in `fire_triggers'
from C:/Users/D3TzH/.vagrant.d/gems/2.4.4/gems/vagrant-triggers-0.5.3/lib/vagrant-triggers/action/trigger.rb:18:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builder.rb:116:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/runner.rb:102:in `block in run'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/util/busy.rb:19:in `busy'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/runner.rb:102:in `run'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/machine.rb:238:in `action_raw'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/machine.rb:209:in `block in action'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/environment.rb:615:in `lock'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/machine.rb:195:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/machine.rb:195:in `action'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
With the release of Vagrant 2.1.0, the functionality of the vagrant-triggers plugin was incorporated into the core Vagrant product. As noted in the Vagrant 2.1.0 announcement, the plugin is now incompatible with versions of Vagrant >= 2.1.0:
This work was heavily inspired by the fantastic community plugin vagrant-triggers by #emyl. It is a complete rewrite of the plugin, so the two are not compatible.
Given that situation, the error is most likely fixed by uninstalling the third party vagrant-triggers plugin.
Windows 10.
When run vagrant up, got these errors:
==> centos: Destroying VM and associated drives...
C:/Users/hi/.vagrant.d/gems/2.2.5/gems/daemons-1.2.4/lib/daemons/daemonize.rb:10:in `fork': fork() function is unimplemented on this machine (NotImplementedError)
from C:/Users/hi/.vagrant.d/gems/2.2.5/gems/daemons-1.2.4/lib/daemons/daemonize.rb:10:in `safefork'
from C:/Users/hi/.vagrant.d/gems/2.2.5/gems/daemons-1.2.4/lib/daemons/daemonize.rb:45:in `call_as_daemon'
from C:/Users/hi/.vagrant.d/gems/2.2.5/gems/daemons-1.2.4/lib/daemons/application.rb:270:in `start_proc'
from C:/Users/hi/.vagrant.d/gems/2.2.5/gems/daemons-1.2.4/lib/daemons/application.rb:296:in `start'
from C:/Users/hi/.vagrant.d/gems/2.2.5/gems/daemons-1.2.4/lib/daemons/controller.rb:56:in `run'
from C:/Users/hi/.vagrant.d/gems/2.2.5/gems/daemons-1.2.4/lib/daemons.rb:197:in `block in run_proc'
from C:/Users/hi/.vagrant.d/gems/2.2.5/gems/daemons-1.2.4/lib/daemons/cmdline.rb:92:in `call'
from C:/Users/hi/.vagrant.d/gems/2.2.5/gems/daemons-1.2.4/lib/daemons/cmdline.rb:92:in `catch_exceptions'
from C:/Users/hi/.vagrant.d/gems/2.2.5/gems/daemons-1.2.4/lib/daemons.rb:196:in `run_proc'
from C:/Users/hi/.vagrant.d/gems/2.2.5/gems/vagrant-dns-1.1.0/lib/vagrant-dns/service.rb:26:in `run!'
from C:/Users/hi/.vagrant.d/gems/2.2.5/gems/vagrant-dns-1.1.0/lib/vagrant-dns/service.rb:17:in `start!'
from C:/Users/hi/.vagrant.d/gems/2.2.5/gems/vagrant-dns-1.1.0/lib/vagrant-dns/service.rb:52:in `restart!'
from C:/Users/hi/.vagrant.d/gems/2.2.5/gems/vagrant-dns-1.1.0/lib/vagrant-dns/restart_middleware.rb:14:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/plugins/providers/virtualbox/action/check_guest_additions.rb:49:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/lib/vagrant/action/warden.rb:34:in `call'
from C:/Users/hi/.vagrant.d/gems/2.2.5/gems/vagrant-vbguest-0.13.0/lib/vagrant-vbguest/middleware.rb:31:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/lib/vagrant/action/warden.rb:34:in `call'
from C:/Users/hi/.vagrant.d/gems/2.2.5/gems/vagrant-proxyconf-1.5.2/lib/vagrant-proxyconf/action/only_once.rb:33:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/plugins/providers/virtualbox/action/customize.rb:40:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/lib/vagrant/action/builtin/wait_for_communicator.rb:71:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.2/plugins/providers/virtualbox/action/customize.rb:40:in `call'
I have tried to find some solution from GitHub issues:
https://github.com/vagrant-landrush/landrush/issues/16
Got no idea.
Also tried to install this:
gem install win32-process
The same result.
So I don't know the real problem.
It has been reported that the vagrant-dns plugin can cause this issue on Windows. If it is installed, try uninstalling it.
If that isn't an option, Windows 10 has the Windows Subsystem for Linux feature that you can install. This will allow you to leverage one of the Unix Distro apps in the Windows store to install a bash shell. This will allow you to run your app in a Linux environment, effectively enabling Fork()
I try to run following command:
vagrant plugin install vagrant-librarian-chef
Installing the 'vagrant-librarian-chef' plugin. This can take a few minutes...
/usr/lib/ruby/1.9.1/rubygems/installer.rb:388:in `ensure_required_ruby_version_met': public_suffix requires Ruby version >= 2.0. (Gem::InstallError)
from /usr/lib/ruby/1.9.1/rubygems/installer.rb:156:in `install'
from /usr/lib/ruby/1.9.1/rubygems/dependency_installer.rb:297:in `block in install'
from /usr/lib/ruby/1.9.1/rubygems/dependency_installer.rb:270:in `each'
from /usr/lib/ruby/1.9.1/rubygems/dependency_installer.rb:270:in `each_with_index'
from /usr/lib/ruby/1.9.1/rubygems/dependency_installer.rb:270:in `install'
from /usr/share/vagrant/plugins/commands/plugin/action/install_gem.rb:65:in `block in call'
from /usr/share/vagrant/plugins/commands/plugin/gem_helper.rb:42:in `block in with_environment'
from /usr/lib/ruby/1.9.1/rubygems/user_interaction.rb:40:in `use_ui'
from /usr/share/vagrant/plugins/commands/plugin/gem_helper.rb:41:in `with_environment'
from /usr/share/vagrant/plugins/commands/plugin/action/install_gem.rb:52:in `call'
from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
from /usr/share/vagrant/plugins/commands/plugin/action/bundler_check.rb:20:in `call'
from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
from /usr/lib/ruby/vendor_ruby/vagrant/action/builder.rb:116:in `call'
from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:69:in `block in run'
from /usr/lib/ruby/vendor_ruby/vagrant/util/busy.rb:19:in `busy'
from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:69:in `run'
from /usr/share/vagrant/plugins/commands/plugin/command/base.rb:17:in `action'
from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:27:in `execute'
from /usr/share/vagrant/plugins/commands/plugin/command/root.rb:56:in `execute'
from /usr/lib/ruby/vendor_ruby/vagrant/cli.rb:38:in `execute'
from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:484:in `cli'
from /usr/bin/vagrant:127:in `<main>'
I am trying this on Ubuntu 14.04
I have been able to sucessfully install the following vagrant plugins:
vagrant-vbguest
vagrant-omnibus
vagrant-triggers
vagrant-hostmanager
As far as I can read there, you are using ruby 1.9.1 and the error message is that you need at least ruby 2.0 for that plugin.
Try updating ruby to a newer version. Also try using a tool like rbenv to manage multiple ruby versions, in case you need ruby 1.9.1 for future projects.
I'm trying to vagrant up a custom box in my local Mac machine. Because of an issue with VirtualBox's version, I had to format and reinstall OSx. I've installed Chef DK, Vagrant and installed the berkshelf plugin. When I try to vagrant up, I get the following error:
Bringing machine 'default' up with 'virtualbox' provider...
/opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- bundler (LoadError)
from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/util/env.rb:1:in `<top (required)>'
from /Users/cdelgado/.vagrant.d/gems/2.2.5/gems/vagrant-berkshelf-5.1.1/lib/vagrant-berkshelf/helpers.rb:62:in `berks'
from /Users/cdelgado/.vagrant.d/gems/2.2.5/gems/vagrant-berkshelf-5.1.1/lib/vagrant-berkshelf/action/check.rb:33:in `berkshelf_version_check!'
from /Users/cdelgado/.vagrant.d/gems/2.2.5/gems/vagrant-berkshelf-5.1.1/lib/vagrant-berkshelf/action/check.rb:16:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/builder.rb:116:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/runner.rb:66:in `block in run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/util/busy.rb:19:in `busy'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/runner.rb:66:in `run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/builtin/call.rb:53:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/builder.rb:116:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/runner.rb:66:in `block in run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/util/busy.rb:19:in `busy'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/runner.rb:66:in `run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/machine.rb:225:in `action_raw'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/machine.rb:200:in `block in action'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/environment.rb:567:in `lock'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/machine.rb:186:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/machine.rb:186:in `action'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
from /opt/vagrant/embedded/gems/gems/logging-2.1.0/lib/logging/diagnostic_context.rb:450:in `call'
My current setup is:
Vagrant Version 1.9.0
Chef Development Kit Version: 1.0.3
chef-client version: 12.16.42
delivery version: master (83358fb62c0f711c70ad5a81030a6cae4017f103)
berks version: 5.2.0
kitchen version: 1.13.2
vagrant-berkshelf (5.1.1)
vagrant-omnibus (1.5.0)
vagrant-share (1.1.6)
When I disable berkshelf in the recipe it runs, but obviously the dependencies don't work.
If I downgrade the berkshelf plugin to 5.0.0 I get a different error:
Bringing machine 'default' up with 'virtualbox' provider...
/Users/cdelgado/.vagrant.d/gems/2.2.5/gems/vagrant-berkshelf-5.0.0/lib/vagrant-berkshelf/helpers.rb:62:in `berks': uninitialized constant VagrantPlugins::Berkshelf::Helpers::Bundler (NameError)
from /Users/cdelgado/.vagrant.d/gems/2.2.5/gems/vagrant-berkshelf-5.0.0/lib/vagrant-berkshelf/action/check.rb:33:in `berkshelf_version_check!'
from /Users/cdelgado/.vagrant.d/gems/2.2.5/gems/vagrant-berkshelf-5.0.0/lib/vagrant-berkshelf/action/check.rb:16:in `call'
I've been googling for days now with no luck, please help.
After many days googling with a colleague, we compared our versions and narrowed the problem down to the Vagrant version. I was running 1.9.0 and he was running 1.8.4. Since the same recipe did work on his machine, I downgraded Vagrant to his version and voilá, it worked. We still don't know what's the exact difference and why does this problem occur, but this will do for now.
I hope this helps whoever stumbles into this problem.
You need to upgrade or install your vagrant-share plugin.
Run this command:
vagrant plugin install vagrant-share --plugin-version 1.1.8
Adapt the version based on the newest or desired one.
If it doesn't work for you (worked for me), there is an issue on GitHub about this
here.
Note, I'm running this on a Windows Environment.
I'm working behind a corporate proxy, and trying to get the vagrant-proxyconf plug-in working so the vagrant machines can be set up to work through a proxy. However, on executing vagrant plugin install vagrant-proxyconf I got the following error:
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:
Could not fetch specs from http://gems.hashicorp.com/
Retrying source fetch due to error (2/3): Bundler::HTTPError Could not fetch specs from http://gems.hashicorp.com/Retrying source fetch due to error (3/3): Bundler::HTTPError Could not fetch specs from http://gems.hashicorp.com/
Figuring it was probably a proxy issue, I tried setting my environment variable:
set HTTP_PROXY="http://username:password#proxy:port"
After re-executing the plug-in install command, I got a different error:
C:/Vagrant/embedded/lib/ruby/2.0.0/uri/common.rb:176:in `split': bad URI(is not
URI?): http://"http://username:password#proxy:port" (URI::InvalidURIError)
from C:/Vagrant/embedded/lib/ruby/2.0.0/uri/common.rb:211:in `parse'
from C:/Vagrant/embedded/lib/ruby/2.0.0/uri/common.rb:747:in `parse'
from C:/Vagrant/embedded/lib/ruby/2.0.0/uri/common.rb:996:in `URI'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/vendor/net/
http/persistent.rb:908:in `proxy_from_env'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/vendor/net/
http/persistent.rb:858:in `proxy='
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/vendor/net/
http/persistent.rb:528:in `initialize'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/fetcher.rb:
113:in `new'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/fetcher.rb:
113:in `connection'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/fetcher.rb:
103:in `initialize'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/source/ruby
gems.rb:262:in `new'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/source/ruby
gems.rb:262:in `block in remote_specs'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/source/ruby
gems.rb:262:in `map'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/source/ruby
gems.rb:262:in `remote_specs'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/source/ruby
gems.rb:202:in `fetch_specs'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/source/ruby
gems.rb:66:in `specs'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/definition.
rb:216:in `block (2 levels) in index'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/definition.
rb:213:in `each'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/definition.
rb:213:in `block in index'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/index.rb:9:
in `build'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/definition.
rb:209:in `index'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/definition.
rb:203:in `resolve'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/definition.
rb:133:in `specs'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/definition.
rb:122:in `resolve_remotely!'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/installer.r
b:76:in `run'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/installer.r
b:15:in `install'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/bundler.rb:
226:in `block in internal_install'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/bundler.rb:
284:in `block in with_isolated_gem'
from C:/Vagrant/embedded/lib/ruby/2.0.0/rubygems/user_interaction.rb:40:
in `use_ui'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/bundler.rb:
283:in `with_isolated_gem'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/bundler.rb:
225:in `internal_install'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/bundler.rb:
92:in `install'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/plugin/mana
ger.rb:62:in `block in install_plugin'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/plugin/mana
ger.rb:72:in `call'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/plugin/mana
ger.rb:72:in `install_plugin'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/plugins/commands/plugin
/action/install_gem.rb:37:in `call'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/ward
en.rb:34:in `call'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/buil
der.rb:116:in `call'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/runn
er.rb:66:in `block in run'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/util/busy.r
b:19:in `busy'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/runn
er.rb:66:in `run'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/plugins/commands/plugin
/command/base.rb:14:in `action'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/plugins/commands/plugin
/command/install.rb:32:in `block in execute'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/plugins/commands/plugin
/command/install.rb:31:in `each'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/plugins/commands/plugin
/command/install.rb:31:in `execute'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/plugins/commands/plugin
/command/root.rb:56:in `execute'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/cli.rb:42:i
n `execute'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/environment
.rb:292:in `cli'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/bin/vagrant:174:in `<ma
in>'
Note the error:
C:/Vagrant/embedded/lib/ruby/2.0.0/uri/common.rb:176:in 'split': bad URI(is not URI?): http://"http://username:password#proxy:port" (URI::InvalidURIError) from C:/Vagrant/embedded/lib/ruby/2.0.0/uri/common.rb:211:in parse'
Seems it's interpreting the environment variable incorrectly and having issues interpreting it? Anyone know how to address this issue?
You don't probably even need the quotes (unless the password includes some funny characters). So you could just try:
set HTTP_PROXY=http://username:password#proxy:port
If you need the quotes, the correct form is:
set "HTTP_PROXY=http://username:password#proxy:port"