logo标签列表

Vagrant在Windows 7上卡住了

vagrant
15

vagrant up 在Windows 7上似乎卡住了

我的Vagrant文件

VAGRANTFILE_API_VERSION = "2"

ENV['VAGRANT_DEFAULT_PROVIDER'] = 'docker'

Vagrant.configure("2") do |config|

  config.vm.network "forwarded_port", guest: 80, host: 8080, auto_correct: true

  config.vm.define "elk" do |elk|
    elk.vm.synced_folder "./www", "/var/www"
    elk.vm.provider "docker" do |d|
      d.build_dir = "./Docker"
    end
  end
end

vagrant up --debug

==> elk: Syncing folders to the host VM...
 INFO machine: Calling action: sync_folders on provider VirtualBox (3c7dc34c-6fcf-4ace-87d1-0602b664e783)
DEBUG environment: Attempting to acquire process-lock: machine-action-740c202843bdf6334148bb69e000ec99
DEBUG environment: Attempting to acquire process-lock: dotlock
 INFO environment: Acquired process lock: dotlock
 INFO environment: Released process lock: dotlock
 INFO environment: Acquired process lock: machine-action-740c202843bdf6334148bb69e000ec99
 INFO environment: Released process lock: machine-action-740c202843bdf6334148bb69e000ec99
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 1 hooks defined.
 INFO runner: Running action: #<Vagrant::Action::Builder:0x3786018>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::SyncedFolders:0x38079d8>
 INFO subprocess: Starting process: ["C:\\windows\\System32\\WindowsPowerShell\\v1.0\\/powershell.EXE", "-NoProfile", "-ExecutionPolicy", "Bypass", "$PSVersionTable.PSVersion.Major"]
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: 2
1个回答
13
升级PowerShell对我有用，但我还必须升级VirtualBox并在安装Vagrant后再次重启计算机。要测试vagrant抱怨的内容，请使用vagrant up --debug命令，这样您就可以获得一些关于它在幕后执行的指示。 - xpagesbeast
这里描述的解决方案：升级Windows管理框架（包括PowerShell）对我有效。然而，随着时间的推移，新版本出现了。我建议不要点击本答案中已经过时的Microsoft链接，而是搜索最新版本的“Windows管理框架”。在我的情况下：Vagrant版本2.0.1和适用于Windows 7 x64的Windows管理框架5.1。 - user3078690
我在5.1版本中更新了WMF，对我来说一切都很正常。 - Harold L. Brown
网页内容由stack overflow 提供, 点击上面的
可以查看英文原文，
原文链接