Laravel Homestead Vagrant未启动

Question

我让我的Vagrant box在我的mac上和小牛一起工作得很好。我在homestead.yaml文件中添加了一个新项目，当我运行vagrant reload时，我收到了以下内容：

Bringing machine 'default' up with 'virtualbox' provider...
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/kernel_v2/config/vm.rb:550:in `initialize': no implicit conversion of nil into String (TypeError)
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/kernel_v2/config/vm.rb:550:in `new'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/kernel_v2/config/vm.rb:550:in `block in validate'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/kernel_v2/config/vm.rb:545:in `each'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/kernel_v2/config/vm.rb:545:in `validate'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/config/v2/root.rb:68:in `block in validate'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/config/v2/root.rb:64:in `each'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/config/v2/root.rb:64:in `validate'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/config_validate.rb:15:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builder.rb:116:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `block in run'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/util/busy.rb:19:in `busy'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `run'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/call.rb:53:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builder.rb:116:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `block in run'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/util/busy.rb:19:in `busy'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `run'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/machine.rb:196:in `action_raw'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/machine.rb:173:in `block in action'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/environment.rb:434:in `lock'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/machine.rb:161:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/machine.rb:161:in `action'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'

我什么也没碰。现在我不能启动它了。有什么想法吗？

Answer 1

在这个封闭的问题上，这个家伙犯了与你相同的错误：

https://github.com/mitchellh/vagrant/issues/3961

看起来他在他的Vagrant文件中有一个错误的语句，导致它在启动时崩溃。也许你的yaml文件中有一个拼写错误或类似的东西？你有没有修改过Vagrant主文件或者甚至是homestead.rb文件？其中任何一个的打字错误或错误都可能导致您的问题。

Answer 2

在这个问题上花了几个小时之后，我刚刚重新初始化了homestead。

1. 删除了现有的homestead文件夹。

rm .homestead

• initialized -rf homestead.

homestead init

• 编辑yaml文件

homestead编辑

• boot up homestead

homestead up

让它启动并运行起来。