ssh身份验证的问题:
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: bridged
==> default: Forwarding ports...
default: 22 => 2222 (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Error: Connection timeout. Retrying...
default: …我想使用ubuntu/xenial64box为两个单独的项目创建两个单独的VM.我在两个单独的项目目录中定义了Vagrantfile,并将行添加config.vm.box = "ubuntu/xenial64"到每个目录中.
第一个盒子成功启动.但是当我vagrant up为第二个项目做的时候,我得到了错误
A VirtualBox machine with the name 'ubuntu-xenial-16.04-cloudimg' already exists.
在Vagrant的文档中,它写得很清楚
为当前用户全局存储框.每个项目都使用一个框作为初始图像进行克隆,并且永远不会修改实际的基本图像.这意味着如果您有两个项目都使用我们刚添加的hashicorp/precise64框,则在一台客户机中添加文件对其他机器没有影响.
为什么我会收到此错误？
我已经检查了其他类似的问题,但我不理解他们删除看似具有相同名称的现有虚拟机的解决方案.根据上面的Vagrant文档引用,这不应该是必要的.我错过了什么吗？
我最近开始在我的本地Wordpress开发环境中使用Virtualbox,Vagrant和VVV.它很光滑.
我遇到的一个问题是,在关闭'流浪汉停止'之后,下次我开始'流浪汉'时我得到了这个错误:
==> default: Setting the name of the VM: vagrant-local
The name of your virtual machine couldn't be set because VirtualBox
is reporting another VM with that name already exists. Most of the
time, this is because of an error with VirtualBox not cleaning up
properly. To fix this, verify that no VMs with that name do exist
(by opening the VirtualBox GUI). If they don't, then look at the
folder in the error message from VirtualBox below and …我跑了一个测试厨房实例,一切都很好,但最后我确实试图用以下方法销毁厨房:
roberto@pc:~$ kitchen destroy
Virtualbox给了我这个错误.
-----> Starting Kitchen (v1.1.1)
-----> Destroying <default-ubuntu-1204>...
[default] Destroying VM and associated drives...
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: Failed to complete #destroy action: [Expected process to exit with [0], but received '1'
---- Begin output of vagrant destroy -f ----
STDOUT: [default] Destroying VM and associated drives...
STDERR: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["unregistervm", "2507bc77-3734-429b-a573-d92fadb80e95", …