boot2docker从Windows 7开始 [英] boot2docker starting in Windows 7

问题描述

我在Windows 7，virtualbox 4.3.26（与boot2docker一起安装）中启动boot2docker有问题。

I am having issues to start boot2docker in windows 7, virtualbox 4.3.26 (installed together with boot2docker).

这是输出

Boot2Docker-cli version: v1.6.0
Git commit: 9894ae9
2015/05/05 17:08:12 executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe showvminfo boot2docker-vm --machinereadable
2015/05/05 17:08:12 executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe guestproperty set boot2docker-vm /VirtualBox/GuestAdd/SharedFolders/MountPrefix /
2015/05/05 17:08:12 executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe guestproperty set boot2docker-vm /VirtualBox/GuestAdd/SharedFolders/MountDir /
2015/05/05 17:08:12 executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe sharedfolder add boot2docker-vm --name c/Users --hostpath C:\Users --automount
VBoxManage.exe: error: Shared folder named 'c/Users' already exists
VBoxManage.exe: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component SessionMachine, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: "CreateSharedFolder(Bstr(name).raw(), Bstr(hostpath).raw(), fWritable, fAutoMount)" at line 1008 of file VBoxManageMisc.cpp
2015/05/05 17:08:12 executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe setextradata boot2docker-vm VBoxInternal2/SharedFoldersEnableSymlinksCreate/c/Users 1
2015/05/05 17:08:12 executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm boot2docker-vm --type headless
Waiting for VM "boot2docker-vm" to power on...
VM "boot2docker-vm" has been successfully started.
2015/05/05 17:08:16 executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe showvminfo boot2docker-vm --machinereadable
Waiting for VM and Docker daemon to start...
.Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connect
ing to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to t
cp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://loc
alhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2
022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (att
empt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0)
.Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connect
ing to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to t
cp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://loc
alhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2
022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (att
empt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0)
.Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connect
ing to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to t
cp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://loc
alhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2
022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (att
empt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0)VM Host-only IP address:
Waiting for Docker daemon to start...
o2015/05/05 17:09:53 executing: C:\Program Files (x86)\Git\bin\ssh.exe ssh -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -p 2022 -i C:\Users\zencv\.ssh\id_boot2docker docker@localhost grep tcp:// /proc/$(cat /var/run/docker.pid)/cmdline

然后挂起..

我的虚拟机配置如下（对不起，在德国）：

My virtualbox config is as follows (sorry, in german):

I尝试了不同的东西，如删除boot2docker-vm，再次下载并重新启动。
另请注意，这似乎与类似的问题不同，例如 Boot2Docker启动失败或停放在windows上的docker不工作 - 在这些情况下，错误消息明确提及虚拟化被禁用，但我的输出中没有看到任何这样的错误。不幸的是，我在一个非常受控的环境中工作。我不能使用任何检查虚拟化是否启用的工具。

I tried different things such as deleting the boot2docker-vm, downloading again and starting again and again. Also please note that this seems to be different from similar issues like Boot2Docker Start up fails or docker on windows not working -- in those cases, the error message explicitly mentions that the virtualization is disabled, but I do not see any such error in my output. Unfortunately, I work in a very controlled env. and I cannot use any tools that check whether virtualization is enabled or not.

推荐答案

这个类似的boot2docker问题提到：

它听起来你可能会在VirtualBox中设置一个迷你boot2docker-vm - 这可能值得打开VirtualBox GUI来删除它，然后尝试：

It sounds like you might have a stray boot2docker-vm set up in VirtualBox -- it's probably worth trying to open the VirtualBox GUI to delete that and try:

boot2docker -v init 
boot2docker -v up

完整的重新安装过程是：

The complete reinstall process is:

docker cask remove virtualbox
docker cask install virtualbox
boot2docker delete
boot2docker init
boot2docker up

还要检查你是否有一个％HOME％定义的环境变量：

Also check if you have a %HOME% environment variable defined:

问题是我的SSH配置。当尝试连接到boot2docker vm时，它使用我的github私钥，而不是boot2docker私钥。

The problem was my SSH Config. When it try to connect to boot2docker vm, it use my github private key and not the boot2docker private key.

我确认它完美无缺。只需更改％HOME％/。ssh / config

我添加了：

I confirm it works perfectly. Just changing %HOME%/.ssh/config
I added:

Host boot2docker
  Hostname localhost
  IdentityFile ~/.ssh/id_boot2docker

这篇关于boot2docker从Windows 7开始的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！