Vagrant将无法在Windows CMD上启动(Errno :: EACCES)
发布时间:2020-12-14 04:17:36 所属栏目:Windows 来源:网络整理
导读:所以我正在使用从这个网站获得的Vagrant Box: https://github.com/edx/configuration/wiki/edX-Developer-Stack 我根据说明进行了设置(虽然我已经修改了,因为我使用的是Windows CMD),当我输入vagrant时,我得到了这个输出: C:UsersUserMy DocumentsMOOC
所以我正在使用从这个网站获得的Vagrant Box:
https://github.com/edx/configuration/wiki/edX-Developer-Stack
我根据说明进行了设置(虽然我已经修改了,因为我使用的是Windows CMD),当我输入vagrant时,我得到了这个输出: C:UsersUserMy DocumentsMOOCSWindowsEDXmy-workspacemy-edx-workspacedevsta 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' 我不太清楚这意味着什么,或者它与Ruby有什么关系.当我在Cygwin上运行它时,它工作正常,但出于测试目的,我必须在Windows CMD上执行此操作. 我也试过禁用我的防病毒软件,并以管理员身份运行CMD.都没有奏效.
我有一个类似的问题.我发现“我的文档”名称实际上是“Documents”文件夹的别名.尝试更改路径,将“Documents”替换为“My Documents”.
(编辑:李大同) 【声明】本站内容均来自网络,其相关言论仅代表作者个人观点,不代表本站立场。若无意侵犯到您的权利,请及时与联系站长删除相关内容! |
相关内容
- Windows上的Autoconf和configure.exe
- windows – 带双引号参数的exec
- windows-7 – 登台新计算机的最佳方式 – 以没有密码的用户
- 纠正整个Windows域中的时间偏差
- 在两台Windows机器之间创建VPN的最佳方法是什么?
- 本地windows上安装protobuf和thrit环境
- windows – 如何以编程方式更改第三个监视器
- windows-server-2008 – 更改Windows SID如何影响SQL Serve
- windows – 汇编中的非法指令
- windows-server-2008-r2 – IPv6主机不响应Neighbor Solici
推荐文章
站长推荐
- windows – 如何创建Win32控件以包含其他Win32控
- windows-phone-7 – 使用MediaStreamSource的WP7
- windows-server-2008 – 您是否必须运行远程桌面
- windows-phone-7 – 在Mango中,是否可以在类库中
- windows – SVN,Apache,Win7 x64 – 在哪里可以找
- 寻找一个好的启用WebDAV的Windows编辑器
- Windows Touch Input WM GESTURE WM TOUCH
- windows-phone-7 – WP7更改应用程序名称
- active-directory – 无法在新站点上将Windows S
- npm ERR!注册表错误解析json – 尝试在Windows
热点阅读