I am trying to setup Laravel homestead on a windows machine according to the documentation here: http://laravel.com/docs/5.0/homestead#installation-and-setup.
However when I get to the 'Launch The Vagrant Box' step I get the following error when I try to 'vagrant up' from cmd:
D:/Homestead/scripts/homestead.rb:4:in `configure': undefined method `[]' for false:FalseClass (NoMethodError)
from D:/Homestead/Vagrantfile:18:in `block in <top (required)>'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/config/v2/loader.rb:37:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/config/v2/loader.rb:37:in `load'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/config/loader.rb:103:in `block (2 levels) in load'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/config/loader.rb:97:in `each'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/config/loader.rb:97:in `block in load'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/config/loader.rb:94:in `each'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/config/loader.rb:94:in `load'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/vagrantfile.rb:28:in `initialize'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:691:in `new'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:691:in `vagrantfile'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:441:in `host'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:207:in `block in action_runner'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/runner.rb:33:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/runner.rb:33:in `run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:428:in `hook'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:673:in `unload'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/bin/vagrant:177:in `ensure in <main>'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.2/bin/vagrant:177:in `<main>'
If I use Cygwin to 'Vagrant up' instead I get this error:
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'laravel/homestead' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
The box 'laravel/homestead' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:
URL: ["https://atlas.hashicorp.com/laravel/homestead"]
Error: Could not resolve host: (nil); Host not found
Should I be using Cygwin or cmd?
How can I fix these errors? I ran'Vagrant box' successfully in cmd (pointing to a local .box file as I am behind a proxy), should I have run it in Cygwin instead?
Edit:
Okay, so If i replace '~' with 'C:/Users/[username]/' that brings running it in cmd inline with running it in Cygwin, so the now both give the same error.
The issue was I had used
vagrant box add laravel [location]
rather than
vagrant box add laravel/homestead [location]
Related
I couldn't find anyone else wrestling with this issue -- all the proxy questions I found are people trying to do this with a proxy.
I'm setting up a Laravel Homestead box. Windows 10, latest versions of Vagrant and VirtualBox.
UPDATE: This seems to be true across other vagrant boxes as well, so now it seems like this is a Vagrant issue and not unique to Homestead.
When I run vagrant box add laravel/homestead, I get this error:
C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/excon-0.78.0/lib/excon/connection.rb:582:in `setup_proxy': Proxy is invalid (Excon::Error::ProxyParse)
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/excon-0.78.0/lib/excon/connection.rb:80:in `initialize'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/excon-0.78.0/lib/excon.rb:142:in `new'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/excon-0.78.0/lib/excon.rb:142:in `new'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant_cloud-3.0.2/lib/vagrant_cloud/client.rb:61:in `initialize'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/plugins/commands/cloud/client/client.rb:35:in `new'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/plugins/commands/cloud/client/client.rb:35:in `initialize'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/plugins/commands/cloud/auth/middleware/add_authentication.rb:34:in `new'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/plugins/commands/cloud/auth/middleware/add_authentication.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/action/warden.rb:48:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/action/builder.rb:149:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/action/runner.rb:89:in `block in run'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/util/busy.rb:19:in `busy'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/action/runner.rb:89:in `run'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/environment.rb:525:in `hook'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/action/builtin/box_add.rb:82:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/action/builtin/box_add.rb:82:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/action/warden.rb:48:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/action/builder.rb:149:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/action/runner.rb:89:in `block in run'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/util/busy.rb:19:in `busy'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/action/runner.rb:89:in `run'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/plugins/commands/box/command/add.rb:78:in `execute'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/plugins/commands/box/command/root.rb:66:in `execute'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/cli.rb:67:in `execute'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/environment.rb:290:in `cli'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/bin/vagrant:205:in `<main>'
Similar error is thrown if I run vagrant halt on another machine.
The first line of the error message suggests that it's a proxy problem, but I'm not behind a proxy:
$ netsh winhttp show proxy
Current WinHTTP proxy settings:
Direct access (no proxy server).
I've tried rebooting and that didn't change anything. Suggestions? Many thanks!
I came across this issue today:
There are Windows environment variables called "http_proxy" and "https_proxy". In my case they were different from the internet options -> connections proxy.
I solved this by deleting the environment variables http_proxy and https_proxy. Then restarted the system.
Afterwards, the executed vagrant from the shell used the correct proxy.pac script and worked as intended.
I am trying to install laravel/homestead however, during the installation I encountered an error with my VBoxManage when I ran the command vagrant up, what can I do to fix this?
Distro: openSUSE Leap 42.1
Vagrant version: 1.8.6
VirtualBox version: 5.0.26_SUSE r108824
The Error:
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["hostonlyif", "create"]
Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: Operation not permitted
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg*)" at line 71 of file VBoxManageHostonly.cpp
Does this have anything to do with permissions? because of Operation not permitted?
I checked the file with ls -l /dev/vboxnetctl and this is what it returned:
crw------- 1 root root 10, 55 Oct 3 07:24 /dev/vboxnetctl
Should I be changing the permission of this file? If so, I want to let you know that I did it before and it still shows an error, but this error is different:
/home/troopy712139/Homestead/scripts/homestead.rb:4:in `configure': undefined method `[]' for nil:NilClass (NoMethodError)
from /home/troopy712139/Homestead/Vagrantfile:30:in `block in <top (required)>'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/config/v2/loader.rb:37:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/config/v2/loader.rb:37:in `load'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/config/loader.rb:113:in `block (2 levels) in load'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/config/loader.rb:107:in `each'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/config/loader.rb:107:in `block in load'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/config/loader.rb:104:in `each'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/config/loader.rb:104:in `load'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/vagrantfile.rb:28:in `initialize'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/environment.rb:746:in `new'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/environment.rb:746:in `vagrantfile'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/environment.rb:492:in `host'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/environment.rb:214:in `block in action_runner'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/runner.rb:33:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/runner.rb:33:in `run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/environment.rb:479:in `hook'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/environment.rb:728:in `unload'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/bin/vagrant:177:in `ensure in <main>'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.6/bin/vagrant:177:in `<main>'
The VBoxManage hostonlyif create command worked once when I ran it in root.
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'vboxnet1' was successfully created
Can you try running sudo vagrant up --provision.
You may also want to check to make sure your paths match up in the Homestead.yaml file
So it seems all I needed to do was make vboxnetctl be owned by me, and restart my computer. I also added vboxdrv to run on startup by running this code:
service vboxdrv start
The error around: /dev/vboxnetctl tells you that your user doesn't have access there.
Try something line:
sudo usermod -a -G vboxusers
Alvaro
I used to start my local VM gc-gw0 with vagrant:
vagrant up gc-gw0
but since today I get this error instead:
/usr/lib/ruby/2.1.0/rubygems/version.rb:202:in `initialize':
Malformed version number string .git (ArgumentError)
from /usr/lib/ruby/2.1.0/rubygems/version.rb:192:in `new'
from /usr/lib/ruby/2.1.0/rubygems/version.rb:192:in `new'
from /usr/lib/ruby/vendor_ruby/vagrant/box_collection.rb:274:in `block (2 levels) in find'
from /usr/lib/ruby/vendor_ruby/vagrant/box_collection.rb:271:in `map'
from /usr/lib/ruby/vendor_ruby/vagrant/box_collection.rb:271:in `block in find'
from /usr/lib/ruby/vendor_ruby/vagrant/box_collection.rb:423:in `block in with_collection_lock'
from /usr/lib/ruby/2.1.0/monitor.rb:211:in `mon_synchronize'
from /usr/lib/ruby/vendor_ruby/vagrant/box_collection.rb:422:in `with_collection_lock'
from /usr/lib/ruby/vendor_ruby/vagrant/box_collection.rb:264:in `find'
from /usr/lib/ruby/vendor_ruby/vagrant/vagrantfile.rb:157:in `block in machine_config'
from /usr/lib/ruby/vendor_ruby/vagrant/vagrantfile.rb:190:in `call'
from /usr/lib/ruby/vendor_ruby/vagrant/vagrantfile.rb:190:in `machine_config'
from /usr/lib/ruby/vendor_ruby/vagrant/vagrantfile.rb:45:in `machine'
from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:503:in `machine'
from /usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:168:in `block in with_target_vms'
from /usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:192:in `call'
from /usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:192:in `block in with_target_vms'
from /usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:174:in `each'
from /usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:174:in `with_target_vms'
from /usr/share/vagrant/plugins/commands/up/command.rb:67:in `block in execute'
from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:239:in `block (2 levels) in batch'
from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:237:in `tap'
from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:237:in `block in batch'
from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:236:in `synchronize'
from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:236:in `batch'
from /usr/share/vagrant/plugins/commands/up/command.rb:58:in `execute'
from /usr/lib/ruby/vendor_ruby/vagrant/cli.rb:42:in `execute'
from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:258:in `cli'
from /usr/bin/vagrant:173:in `<main>'
The strange thing is, I still started it like this yesterday without problem.
I searched a lot for this error but no hints yet. What does this error message mean? Which is the main error in the whole message?
I use
$ vagrant -v
Vagrant 1.6.5
$ ruby -v
ruby 2.1.2p95 (2014-05-08) [i386-linux-gnu]
Vagrantfile and bootstrap-testnode.sh files are here: rubo77/freifunk-gluon-example-node
But I deleted all my vms in virtualbox but still I get this error anytime I want to do anything with vagrant. seems vagrant has some problem itself. So I guess the scripts I tried have nothing to do with this error.
line 202 in /usr/lib/ruby/2.1.0/rubygems/version.rb is this:
def initialize version
raise ArgumentError, "Malformed version number string #{version}" unless
self.class.correct?(version)
#version = version.to_s.strip.gsub("-",".pre.")
#segments = nil
end
So it seems like ruby is checking a .git folder instead of a version number folder
I found out:
I had created a .git repository inside
~/.vagrant.d/boxes/box-cutter-VAGRANTSLASH-debian77-i386
So vagrant tried to read that folder where there should be only folders named by numbers.
I removed that .git folder and it worked
I got an similar vagrant misconfiguration.
For some reason when updating repos on specific configurations of the vagrant files, this can mess up the vagrant boxes. In my case I was upgrading vagrant and virtualbox with some other changes to the vagrantfile.
I had to go to
~/.vagrant.d/boxes/
and erase the old boxes that I had.
I get stuck when I'm trying to run the vagrant up command. I have this local .box file sitting in my local drive and fist ran vagrant init, and then added it. Adding seemed to go fine, but when I tried running vagrant up as shown below, it returns:
C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/uri/common.rb:176:in `split': bad URI(is not URI?): file:C:/Users/burea1124/Projects/theirgoods/CUserurea1124Projectstheirgoodstheirgoods_dev_vm.box (URI::InvalidURIError)
Obviously it looks like I'm supposed to fix the URI somewhere but I have no idea why it looks like that in the first place. Does anybody have any clues to how I can fix this?
C:\Users\burea1124\Projects\theirgoods>vagrant box add theirgoods
C:\Users\burea1124\Projects\theirgoods\theirgoods_dev_vm.box
==> box: Adding box 'theirgoods' (v0) for provider:
box: Downloading: file://C:/Users/burea1124/Projects/theirgoods/theirgoods_dev_vm.box
box: Progress: 100% (Rate: 500M/s, Estimated time remaining: --:--:--)
==> box: Successfully added box 'theirgoods' (v0) for 'virtualbox'!
C:\Users\burea1124\Projects\theirgoods> vagrant up
Bringing
machine'default' up with 'virtualbox' provider...
==> default: Box 'CUserurea1124Projectstheirgoodstheirgoods_dev_vm.box' could not be
found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0 C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/uri/common.rb:176:in
split': bad URI(is not URI?):
file:C:/Users/burea1124/Projects/theirgoods/CUserurea1124Projectstheirgoodstheirgoods_dev_vm.box
(URI::InvalidURIError)
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/uri/common.rb:211:in
parse'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/uri/common.rb:747:in
parse'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/box_add.rb:458:in
metadata_url?'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/box_add.rb:77:in
block in call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/box_add.rb:75:in
map'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/box_add.rb:75:in
call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in
call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builder.rb:116:in
call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in
block in run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/util/busy.rb:19:in
busy'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in
run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/handle_box.rb:79:in
handle_box'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/handle_box.rb:42:in
block in call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/handle_box.rb:36:in
synchronize'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/handle_box.rb:36:in
call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in
call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:95:in
block in finalize_action'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in
call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in
call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builder.rb:116:in
call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in
block in run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/util/busy.rb:19:in
busy'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in
run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/call.rb:53:in
call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in
call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in
call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in
call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builder.rb:116:in
call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in
block in run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/util/busy.rb:19:in
busy'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in
run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/machine.rb:196:in
action_raw'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/machine.rb:173:in
block in action'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/environment.rb:434:in
lock'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/machine.rb:161:in
call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/machine.rb:161:in
action'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/batch_action.rb:82:in
block (2 levels) in run'
It seems that in your Vagrantfile you're referencing the box with the full path, you have to use the box name instead:
config.vm.box = "theirgoods"
This was the top question when I searched for that error. The problem in my case was that I added the box correctly, but I copied over an existing Vagrantfile and forgot to do vagrant init.
So for anyone else with this error, make sure you are doing vagrant init :)
Note - this question is also posted in https://groups.google.com/forum/#!topic/vagrant-up/aZOs1YXmvhI
Setup
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]
EDIT I just installed & updated my %PATH% to use ruby 2.0, but still having the same issue.
On a Windows 7 PC, I was using Vagrant 1.3.5 with VirtualBox 4.3.8, but upgraded to the above versions in order to attempt to fix a shared directory problem - https://groups.google.com/forum/#!topic/vagrant-up/eC72_YXdtYE.
Anyway, after upgrading to the first listed versions, I destroyed my VM with VirtualBox using "Remove / Delete All Files." Then I tried, unsuccessfully, to spin up a VM with 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'
How can I debug this error?
You can install a version of Vagrant-Berkshelf that works with Vagrant 1.4.3
vagrant plugin uninstall vagrant-berkshelf
vagrant plugin install vagrant-berkshelf --plugin-version 1.3.7