【问题标题】:vagrant up not working ubuntu流浪汉不工作ubuntu
【发布时间】:2016-09-08 08:51:25
【问题描述】:

当我在 digitalocean 服务器(ubuntu)上运行 vagrant up 命令时,它会显示以下错误。此命令在本地运行良好,但在服务器上运行不正常。

$ vagrant up


There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["modifyvm", "d2015e22-d634-46d6-9de5-9ca5e9ecea38", "--natpf1", "delete", "ssh", "--natpf1", "delete", "tcp9100", "--natpf1", "delete", "tcp9101", "--natpf1", "delete", "tcp9102", "--natpf1", "delete", "tcp9103", "--natpf1", "delete", "tcp9104", "--natpf1", "delete", "tcp9105"]

Stderr: VBoxManage: error: The machine 'LaunchKit_default_1473257270586_51004' is already locked for a session (or being unlocked)
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee nsISupports
VBoxManage: error: Context: "LockMachine(a->session, LockType_Write)" at line 493 of file VBoxManageModifyVM.cpp

【问题讨论】:

    标签: ubuntu vagrant digital-ocean vagrant-provision


    【解决方案1】:

    VirtualBox 认为您的 VM 仍在运行。

    1. 它可能被进程持有 运行 ps -ef | grep -i "vbox" 并终止与您的 VM 关联的进程(任意)

    2. 如果找不到进程,强制VBox停止VM

      VBoxManage controlvm LaunchKit_default_1473257270586_51004 poweroff
      

    【讨论】:

      猜你喜欢
      • 2023-04-01
      • 1970-01-01
      • 2015-08-25
      • 2016-05-09
      • 2011-10-20
      • 2015-12-13
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      相关资源
      最近更新 更多