boot2docker, начиная с Windows 7

Question

У меня возникли проблемы с запуском boot2docker в windows 7, virtualbox 4.3.26 (устанавливается вместе с 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 

Тогда он висит ..

Мой VirtualBox конфигурации выглядит следующим образом (к сожалению, на немецком языке):

Я пробовал разные вещи например, удаление boot2docker-vm, загрузка снова и запуск снова и снова. Также обратите внимание, что это похоже на аналогичные проблемы, такие как Boot2Docker Start up fails или docker on windows not working. В этом случае в сообщении об ошибке явно указано, что виртуализация отключена, но я не вижу такой ошибки в моем выпуске. К сожалению, я работаю в очень контролируемой среде. и я не могу использовать какие-либо инструменты, которые проверяют, включена ли виртуализация или нет.

Answer 1

Этот similar boot2docker issue упоминает:

Это звучит, как вы могли бы шальная boot2docker-VM создана в VirtualBox - это, наверное, стоит попробовать открыть VirtualBox GUI, чтобы удалить это и попробовать:

boot2docker -v init 
boot2docker -v up 

Весь процесс переустановки является:

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

Также проверьте, если у вас есть переменная %HOME% среды определено:

Проблема была моя SSH Config. Когда он пытается подключиться к boot2docker vm, он использует личный ключ github, а не закрытый ключ boot2docker.

Я подтверждаю, что он отлично работает. Просто изменяя %HOME%/.ssh/config
Я добавил:.

Host boot2docker 
    Hostname localhost 
    IdentityFile ~/.ssh/id_boot2docker