Vagrant wird nicht auf Windows CMD starten (Errno :: EACCES)

Question

Also ich die Vagrant Box von dieser Seite bekommen bin mit: https://github.com/edx/configuration/wiki/edX-Developer-Stack

ich es gemäß den Anweisungen eingerichtet (Obwohl geändert, da ich Windows benutze CMD), und wenn ich in vagrant geben, bekomme ich diese Ausgabe:

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' 

ich nicht sicher bin, was das bedeutet, oder wenn es etwas mit Rubin zu tun. Als ich das auf Cygwin ausführte, funktionierte es gut, aber zu Testzwecken muss ich das unter Windows CMD machen.

Ich habe auch versucht, meine Antivirus deaktivieren und CMD als Administrator ausgeführt. Keine funktionierte.

Answer 1

Vagrant durchläuft jeden Teil des Pfades und überprüft, ob der Pfad korrekt ist. Dies erfordert, zu jedem Teil zu gehen und das Verzeichnis aufzulisten. Es sieht so aus, als hätte Ihr Benutzer unter Windows aus irgendeinem Grund keinen Lesezugriff auf dieses Verzeichnis, was dazu führt, dass dies fehlschlägt.

Die Tatsache, dass eine Stack-Trace angezeigt wird, ist ein Bug mit Vagrant, und ich werde das beheben.

Die Lösung besteht darin, die Berechtigungen aller Komponenten des synchronisierten Ordners zu überprüfen, damit Ihr Benutzer Leseberechtigungen für das Verzeichnis hat.

Answer 2

Ich hatte ein ähnliches Problem mit einem anderen Bild. Sie könnten versuchen, Ihren Arbeitsordner von Eigene Dateien in einen Ordnerpfad zu verschieben, der keine Leerzeichen enthält. Es hat für mich funktioniert.

Answer 3

Ich hatte ein ähnliches Problem. Was ich gefunden habe, ist, dass der Name "Meine Dokumente" eigentlich ein Alias ​​für den Ordner "Dokumente" ist. Versuchen Sie, den Pfad zu ändern und ersetzen Sie "Dokumente" durch "Eigene Dateien".