Vagrant shows errors

Development

AI-generated summary

Vagrant Errors Solved

uwe_keim encountered errors when running vagrant up while following the Guide “Discourse as Your First Rails App”. The errors were due to a compatibility issue with Virtual Box.

After researching, uwe_keim found that downgrading Virtual Box or manually applying a fix could resolve the issue. By following the manual fix steps, uwe_keim was able to successfully run vagrant up.

1

Following the Guide “Discourse as Your First Rails App” (hopefully), I’m having trouble running:

vagrant up

When doing so, I get some messages:

Windows PowerShell
Copyright (C) 2015 Microsoft Corporation. Alle Rechte vorbehalten.

C:\Users\ukeim\Documents\GitHub\discourse [master ≡]> vagrant up
C:/Program Files (x86)/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/util/platform.rb:85:in `block in windows_hyperv_admin?': undefined method `include?' for #<Vagrant::Util::Subprocess::Result:0x378ba00> (NoMethodError)
        from C:/Program Files (x86)/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/util/platform.rb:89:in `call'
        from C:/Program Files (x86)/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/util/platform.rb:89:in `windows_hyperv_admin?'
        from C:/Program Files (x86)/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.4/plugins/providers/hyperv/provider.rb:20:in `usable?'
        from C:/Program Files (x86)/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/environment.rb:381:in `block in default_provider'
        from C:/Program Files (x86)/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/environment.rb:379:in `each'
        from C:/Program Files (x86)/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/environment.rb:379:in `default_provider'
        from C:/Program Files (x86)/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/plugin/v2/command.rb:174:in `block in with_target_vms'
        from C:/Program Files (x86)/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/plugin/v2/command.rb:201:in `call'
        from C:/Program Files (x86)/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/plugin/v2/command.rb:201:in `block in with_target_vms'
        from C:/Program Files (x86)/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/plugin/v2/command.rb:183:in `each'
        from C:/Program Files (x86)/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/plugin/v2/command.rb:183:in `with_target_vms'
        from C:/Program Files (x86)/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.4/plugins/commands/up/command.rb:131:in `install_providers'
        from C:/Program Files (x86)/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.4/plugins/commands/up/command.rb:85:in `execute'
        from C:/Program Files (x86)/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/cli.rb:42:in `execute'
        from C:/Program Files (x86)/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/environment.rb:302:in `cli'
        from C:/Program Files (x86)/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.4/bin/vagrant:174:in `<main>'
C:\Users\ukeim\Documents\GitHub\discourse [master ≡]>

I’m really clueless:

  • Is there anything fundamentally that I forgot?
  • Do I have to set up my own virtual machine first?
  • Is it a problem that I have VMware Workstation also installed?
2

It seems to be an issue with Virtual Box. You could either downgrade Virtual Box or manually do some steps to fix it.

I’ve followed the steps to manually fix it and now vagrant up seems to work.