文档建议反馈控制台
首页
学习
活动
专区
圈层
工具
MCP广场
文章/答案/技术大牛
发布
社区首页 >问答首页 >Vagrant无法在Windows CMD上启动(Errno::EACCES)

问Vagrant无法在Windows CMD上启动(Errno::EACCES)
EN

Stack Overflow用户
提问于 2014-01-08 22:09:44
回答 3查看 3.1K关注 0票数 7

所以我使用的是从这个网站获得的Vagrant Box：https://github.com/edx/configuration/wiki/edX-Developer-Stack

我按照说明进行了设置(尽管进行了修改，因为我使用的是Windows CMD)，当我键入vagrant up时，我会得到以下输出：

代码语言：javascript
复制
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'

我不太确定这是什么意思，或者它是否与Ruby有关。当我在Cygwin上运行时，它工作得很好，但出于测试目的，我必须在Windows CMD上执行此操作。

我还尝试禁用我的防病毒软件，并以管理员身份运行CMD。两种方法都不起作用。

cmd
vagrant
windows
EN

回答 3

Stack Overflow用户

发布于 2014-08-09 01:42:54

我也遇到过类似的问题。我发现"My Documents“名称实际上是"Documents”文件夹的别名。尝试更改路径，将"My Documents“改为"Documents”。

票数 9
EN

Stack Overflow用户

发布于 2014-06-15 17:11:25

使用不同的图像时，我也遇到了类似的问题。您可以尝试将工作文件夹从My Documents移动到其中没有空格的文件夹路径。这对我很管用。

票数 2
EN

Stack Overflow用户

发布于 2014-01-09 00:01:40

Vagrant遍历路径的每个部分，并验证其大小写是否正确。这需要转到每个部分并列出目录。由于某些原因，您在Windows上的用户似乎没有该目录的读取权限，这将导致此操作失败。

显示堆栈跟踪的事实是Vagrant的一个错误，我将修复它。

解决方案是检查同步文件夹的每个组件的权限，以便验证您的用户对该目录具有读取权限。

票数 1
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：

https://stackoverflow.com/questions/20997984

复制
相关文章

相似问题

领券

腾讯云开发者

扫码关注腾讯云开发者

扫码关注腾讯云开发者

领取腾讯云代金券

热门产品

热门推荐

更多推荐

Copyright © 2013 - 2026 Tencent Cloud. All Rights Reserved. 腾讯云 版权所有 

深圳市腾讯计算机系统有限公司 ICP备案/许可证号：粤B2-20090059 粤公网安备44030502008569号

腾讯云计算（北京）有限责任公司 京ICP证150476号 |  京ICP备11018762号

问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档