从Vagrant 1.3.5升级到1.4.3。在“vagrant Berkshellf”插件上失败

注意-此问题也发布在

设置

C:\Users\Kevin>vagrant -v
Vagrant 1.4.3

C:\Users\Kevin>VBoxManage -version # VirtualBox version
4.3.10r93012

C:\Users\Kevin>vagrant plugin list
vagrant-berkshelf (2.0.0)
vagrant-omnibus (1.3.1)
vagrant-vbguest (0.10.0)

C:\Users\Kevin>ruby -v
ruby 1.9.3p484 (2013-11-22) [i386-mingw32]

编辑我刚刚安装并更新了我的%PATH%以使用ruby 2.0，但仍然存在同样的问题

在一台

Windows7

PC上，我将

Vagrant 1.3.5

与

VirtualBox 4.3.8

一起使用，但升级到上述版本以尝试修复共享目录问题-

无论如何，升级到第一个列出的版本后，我用VirtualBox使用“删除/删除所有文件”销毁了我的虚拟机。然后我尝试用

vagrant up

启动虚拟机，但没有成功：

Bringing machine 'default' up with 'virtualbox' provider...
C:/Users/Kevin/.vagrant.d/gems/gems/vagrant-berkshelf-2.0.0/lib/berkshelf/vagrant/env.rb:16:in `initialize': undefined method `opts' for #<Vagrant::
UI::Colored:0x565e7c8> (NoMethodError)
        from C:/Users/Kevin/.vagrant.d/gems/gems/vagrant-berkshelf-2.0.0/lib/berkshelf/vagrant/action.rb:57:in `new'
        from C:/Users/Kevin/.vagrant.d/gems/gems/vagrant-berkshelf-2.0.0/lib/berkshelf/vagrant/action.rb:57:in `block in setup'
        from C:/Users/Kevin/.vagrant.d/gems/gems/vagrant-berkshelf-2.0.0/lib/berkshelf/vagrant/action.rb:56:in `tap'
        from C:/Users/Kevin/.vagrant.d/gems/gems/vagrant-berkshelf-2.0.0/lib/berkshelf/vagrant/action.rb:56:in `setup'
        from C:/Users/Kevin/.vagrant.d/gems/gems/vagrant-berkshelf-2.0.0/lib/berkshelf/vagrant/plugin.rb:15:in `provision'
        from C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:45:in `call'
        from C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:45:in `block (2 levels) in run'
        from C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:44:in `tap'
        from C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:44:in `block in run'
        from C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:43:in `map'
        from C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:43:in `run'
        from C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/machine.rb:147:in `action'
        from C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/batch_action.rb:63:in `block (2 levels) in run'

正在使用“virtualbox”提供程序启动计算机“默认”。。。
C:/Users/Kevin/.vagrant.d/gems/gems/vagrant-berkself-2.0.0/lib/berkself/vagrant/env.rb:16:in“initialize”：未定义的方法“opts”用于#（NoMethodError）
来自C:/Users/Kevin/.vagrant.d/gems/gems/vagrant-berkself-2.0.0/lib/berkself/vagrant/action.rb:57:in“new”
来自C:/Users/Kevin/.vagrant.d/gems/gems/vagrant-berkself-2.0.0/lib/berkself/vagrant/action.rb:57:“设置中的块”
来自C:/Users/Kevin/.vagrant.d/gems/gems/vagrant-berkself-2.0.0/lib/berkself/vagrant/action.rb:56:in'tap'
来自C:/Users/Kevin/.vagrant.d/gems/gems/vagrant-berkself-2.0.0/lib/berkself/vagrant/action.rb:56:在“设置”中
来自C:/Users/Kevin/.vagrant.d/gems/gems/vagrant-berkself-2.0.0/lib/berkself/vagrant/plugin.rb:15:in“provision”
来自C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/Vagrant-1.4.3/lib/Vagrant/action/runner.rb:45:in'call'
来自C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/Vagrant-1.4.3/lib/Vagrant/action/runner.rb:45:“运行中的块（2个级别）”中
来自C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/Vagrant-1.4.3/lib/Vagrant/action/runner.rb:44:in'tap'
来自C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/Vagrant-1.4.3/lib/Vagrant/action/runner.rb:44:在“运行中的块”中
来自C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/Vagrant-1.4.3/lib/Vagrant/action/runner.rb:43:in'map'
来自C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/Vagrant-1.4.3/lib/Vagrant/action/runner.rb:43:in'run'
来自C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/Vagrant-1.4.3/lib/Vagrant/machine.rb:147:正在“行动”
来自C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/Vagrant-1.4.3/lib/Vagrant/batch_action.rb:63:“运行中的块（2个级别）”中

---

如何调试此错误？

您可以安装适用于Vagrant 1.4.3的Vagrant Berkshellf版本

流浪插件卸载流浪软件
vagrant插件安装vagrant berkshelf——插件版本1.3.7

您可以安装与Vagrant 1.4.3配合使用的Vagrant Berkshellf版本

流浪插件卸载流浪软件
vagrant插件安装vagrant berkshelf——插件版本1.3.7

这个问题似乎离题了，因为它已经在上报告、回答并关闭。我会关闭这个，但是人们查看这篇文章，然后查看你的答案是否有用，@Seth？这个问题似乎离题了，因为它已经在上报告、回答并关闭。我会关闭这个，但是人们浏览这篇文章，然后看到你的答案，@Seth，有用吗？