Vagrant does not start on Windows CMD (Errno :: EACCES)

So, I use the Vagrant Box obtained from this site: https://github.com/edx/configuration/wiki/edX-Developer-Stack

I installed it according to the instructions (although modified since I use Windows CMD), and when I type vagrant up, I get this output:

C:\Users\User\My Documents\MOOCS\WindowsEDX\my-workspace\my-edx-workspace\devsta ck>vagrant up Bringing machine 'default' up with 'virtualbox' provider... [default] Importing base box 'empanada-devstack'... [default] Matching MAC address for NAT networking... [default] Setting the name of the VM... [default] Clearing any previously set forwarded ports... [default] Destroying VM and associated drives... [default] Running cleanup tasks for 'shell' provisioner... C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/util/platform. rb:75:in `open': Permission denied - C:/Users/User/My Documents (Errno::EACCES) from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/u til/platform.rb:75:in `entries' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/u til/platform.rb:75:in `block in fs_real_path' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/u til/platform.rb:74:in `each' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/u til/platform.rb:74:in `fs_real_path' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builtin/synced_folders.rb:56:in `block (2 levels) in call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builtin/synced_folders.rb:40:in `each' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builtin/synced_folders.rb:40:in `block in call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builtin/synced_folders.rb:39:in `each' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builtin/synced_folders.rb:39:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builtin/synced_folder_cleanup.rb:28:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/provi ders/virtualbox/action/prepare_nfs_valid_ids.rb:12:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builtin/handle_forwarded_port_collisions.rb:118:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/provi ders/virtualbox/action/prepare_forwarded_port_collision_params.rb:30:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builtin/env_set.rb:19:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builtin/provision.rb:52:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/provi ders/virtualbox/action/clear_forwarded_ports.rb:13:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/provi ders/virtualbox/action/set_name.rb:48:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/provi ders/virtualbox/action/clean_machine_folder.rb:17:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/provi ders/virtualbox/action/check_accessible.rb:18:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:95:in `block in finalize_action' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builder.rb:116:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/runner.rb:69:in `block in run' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/u til/busy.rb:19:in `busy' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/runner.rb:69:in `run' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builtin/call.rb:51:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:95:in `block in finalize_action' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builder.rb:116:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/runner.rb:69:in `block in run' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/u til/busy.rb:19:in `busy' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/runner.rb:69:in `run' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builtin/call.rb:51:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:95:in `block in finalize_action' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builder.rb:116:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/runner.rb:69:in `block in run' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/u til/busy.rb:19:in `busy' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/runner.rb:69:in `run' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builtin/call.rb:51:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builtin/config_validate.rb:25:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/provi ders/virtualbox/action/check_virtualbox.rb:17:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builtin/call.rb:57:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builtin/config_validate.rb:25:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builtin/call.rb:57:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/provi ders/virtualbox/action/check_virtualbox.rb:17:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/warden.rb:34:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/builder.rb:116:in `call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/runner.rb:69:in `block in run' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/u til/busy.rb:19:in `busy' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/a ction/runner.rb:69:in `run' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/m achine.rb:147:in `action' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/b atch_action.rb:63:in `block (2 levels) in run' 

I'm not too sure what this means, or if it has anything to do with Ruby. When I ran this on Cygwin, it worked fine, but for testing I have to do this on Windows CMD.

I also tried to disable my antivirus and run CMD as an administrator. Nothing worked.

+7
windows cmd vagrant
source share
3 answers

I had a similar problem. I found that the name “My Documents” is actually an alias for the “Documents” folder. Try changing the path by replacing Documents with My Documents.

+9
source share

I had a similar problem using a different image. You can try moving the working folder from My Documents to the path to a folder that has no spaces. It worked for me.

+2
source share

A tramp goes through every part of the path and checks that he is properly circled. This requires a transition to each part and listing of the catalog. It appears that your Windows user for some reason does not have read access to this directory, which leads to a crash.

The fact that the stack trace is shown is a bug with Vagrant, and I will fix it.

The solution is to check permissions for each component of the synchronized folder to make sure that the user has read permissions in the directory.

+1
source share

All Articles