Cannot create host-only adapter with VBox 5 on Windows 10 (using administrative shell)

[hheimbuerger]

Environment:

• Windows 10 build 10162 (basically the RC1)
• VirtualBox 5.0 (final)
• docker-machine latest as of 2015-07-13 (downloaded from the nightly builds, because VBox 5 needs this fix)

In an administrative command prompt (Win-X -> Command Prompt (Admin)), trying to create a VirtualBox boot2docker vm fails when attempting to create a host-only adapter:

C:\Users\myuser\Downloads>docker-machine_windows_amd64.exe create --driver virtualbox dev -D
Creating CA: C:\Users\myuser\.docker\machine\certs\ca.pem
Creating client certificate: C:\Users\myuser\.docker\machine\certs\cert.pem
executing: c:\Program Files\Oracle\VirtualBox\VBoxManage.exe
STDOUT: Oracle VM VirtualBox Command Line Management Interface Version 5.0.0
(C) 2005-2015 Oracle Corporation
All rights reserved.

Usage:

  VBoxManage [<general option>] <command>

[... snip entire VBoxManage syntax help ...]

STDERR:
Image cache does not exist, creating it at C:\Users\myuser\.docker\machine\cache...
No default boot2docker iso found locally, downloading the latest release...
Downloading https://github.com/boot2docker/boot2docker/releases/download/v1.7.0/boot2docker.iso to C:\Users\myuser\.docker\machine\cache\boot2docker.iso...
Creating VirtualBox VM...
Creating SSH key...
Creating disk image...
Creating 20000 MB hard disk image...
Converting from raw image file="stdin" to file="C:\Users\myuser\.docker\machine\machines\dev\disk.vmdk"...
Creating dynamic image with size 20971520000 bytes (20000MB)...
executing: c:\Program Files\Oracle\VirtualBox\VBoxManage.exe createvm --basefolder C:\Users\myuser\.docker\machine\machines\dev --name dev --register
STDOUT: Virtual machine 'dev' is created and registered.
UUID: 8b4e1083-2ad1-4a75-bc64-ce6b20ad440c
Settings file: 'C:\Users\myuser\.docker\machine\machines\dev\dev\dev.vbox'

STDERR:
VM CPUS: 1
VM Memory: 1024
executing: c:\Program Files\Oracle\VirtualBox\VBoxManage.exe modifyvm dev --firmware bios --bioslogofadein off --bioslogofadeout off --bioslogodisplaytime 0 --biosbootmenu disabled --ostype Linux26_64 --cpus 1 --memory 1024 --acpi on --ioapic on --rtcuseutc on --natdnshostresolver1 off --natdnsproxy1 off --cpuhotplug off --pae on --hpet on --hwvirtex on --nestedpaging on --largepages on --vtxvpid on --accelerate3d off --boot1 dvd
STDOUT:
STDERR:
executing: c:\Program Files\Oracle\VirtualBox\VBoxManage.exe modifyvm dev --nic1 nat --nictype1 82540EM --cableconnected1 on
STDOUT:
STDERR:
using 192.168.99.1 for dhcp address
executing: c:\Program Files\Oracle\VirtualBox\VBoxManage.exe list hostonlyifs
STDOUT: Name:            VirtualBox Host-Only Ethernet Adapter #11
GUID:            c1389c26-1670-4cb8-97c6-974c8f039d00
DHCP:            Disabled
IPAddress:       192.168.59.99
NetworkMask:     255.255.255.0
IPV6Address:     fe80:0000:0000:0000:f540:67b5:0465:b90d
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:00
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #11


STDERR:
executing: c:\Program Files\Oracle\VirtualBox\VBoxManage.exe hostonlyif create
STDOUT:
STDERR: 0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 70 of file VBoxManageHostonly.cpp

Error creating machine: exit status 1
You will want to check the provider to make sure the machine and associated resources were properly removed.

[nathanleclaire]

Thanks for reporting this issue. I'll look into it.

[sakai135]

I'm having the same issue with Windows 10 build 10240 and VirtualBox 5.0. It seems to be this VirtualBox issue #14040. Just running VBoxManage.exe hostonlyif create alone results in an error.

I have been able to bypass the issue by setting the IP address on the adapter manually to match the HostOnlyCIDR value.

docker-machine -D create -d virtualbox --virtualbox-hostonly-cidr 192.168.56.1/24 dev

[hheimbuerger]

Yeah, that's similar to how I've been solving it, too.

I'm also having occasional routing errors (the correct routing entries disappear) with the host-only adapter, which might be related to all of this.

[henriiik]

Thanks for sharing your solution @sakai135, I was having the same problem. :)

I also had to enable DHCP server on the network interface to get it up and running.

I can also confirm this, on Win 10, build 10240
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 70 of file VBoxManageHostonly.cpp

This is fixed when, as above, I input the expected IP address in the Host-Only NIC configuration. I did not have to do anything with DHCP.

[hheimbuerger]

Possible cause in VirtualBox 5.0: https://www.virtualbox.org/ticket/14040

[vladimir-barsuchenko]

Hi, I'm new to all these "docker things" and have some troubles here. I'm using Windows 10x64 10162 build. Virtual Box 5.0.0 r101573
I did everything as you said:

1. downloaded new version of docker-machine
2. Ran docker-machine_windows_amd64.exe -D create -d virtualbox --virtualbox-hostonly-cidr 192.168.56.1/24 dev
3. I had nothing with DHCP server as @henriiik mentioned above

It was fine until

STDERR:
Error dialing TCP: ssh: handshake failed: WSARecv tcp 127.0.0.1:49751: An existing connection was forcibly closed by the remote host.
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: EOF
Error dialing TCP: ssh: handshake failed: WSARecv tcp 127.0.0.1:49803: An established connection was aborted by the software in your host machine.
Error dialing TCP: ssh: handshake failed: EOF
SSH returned: 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 08:00:27:41:85:25 brd ff:ff:ff:ff:ff:ff
inet6 fe80::a00:27ff:fe41:8525/64 scope link
valid_lft forever preferred_lft forever

END SSH
.....
.....
.....
ERROR getting IP: No IP address found 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 08:00:27:41:85:25 brd ff:ff:ff:ff:ff:ff
inet6 fe80::a00:27ff:fe41:8525/64 scope link
valid_lft forever preferred_lft forever

Error creating machine: Maximum number of retries (5) exceeded You will want to check the provider to make sure the machine and associated resources were properly removed.

However, VM boots good and
$ docker version from VM command line gives me next

Client version: 1.7.1
Client API version: 1.19
Go version(client): go1.4.2
Git commit(client): 786b29d
OS/Arch(client): linux/amd64
Server version: 1.7.1
Server API version: 1.19
Go version (server): go1.4.2
Git commit(server): 786b29d
OS/Arch(server): linux/amd64

But when i'm running
$ eval "$(docker-machine_windows_amd64.exe env dev)"
from my msysgit 1.95 nothing happens. Git waits for something

Then i rebooted my msysgit and tried
/e/ChromeNew/docker-machine_windows_amd64.exe ls
NAME ACTIVE DRIVER STATE URL SWARM
dev virtualbox Stopped

Why Stopped?
Then i powered off my VM and ran
$ /e/ChromeNew/docker-machine_windows_amd64.exe start dev
Starting VM...
Maximum number of retries (5) exceeded
Started machines may have new IP addresses. You may need to re-run the docker-machine env command.

After that I started dev VM manually from Virtual Box and had error

Failed to open a session for the virtual machine dev

Details:
The VM session was aborted.

Result Code:
E_FAIL (0x80004005)
Component:
SessionMachine
Interface:
ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

Have i something misunderstood?
Help me please

Thanks in advance

[sakai135]

@levgaas Yours seems like a separate issue. Install build 10240 and see what happens. 10162 is pretty outdated.

I'm using Vagrant, not Docker, but my workaround was to assign a static IP
on the bridged interface and explicitly specify the correct adapter in the
public network section of the Vagrantfile.

Storm Chaser Scott Roberts
KSStorm.info
-- from mobile device
On Jul 28, 2015 17:12, "Keiichi Shimamura" notifications@github.com wrote:

@levgaas https://github.com/levgaas Yours seems like a separate issue.
Install build 10240 and see what happens. 10162 is pretty outdated.

—
Reply to this email directly or view it on GitHub
#1521 (comment).

[vladimir-barsuchenko]

@sakai135 After upgrading to 10240 build.
docker-machine_windows_amd64.exe -D create -d virtualbox --virtualbox-hostonly-cidr 192.168.56.1/24 dev gives me author`s error

Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 70 of file VBoxManageHostonly.cpp

I have the adapter with specified IPv4 address(192.168.56.1) but every time when i run docker-machine_windows_amd64.exe -D create -d virtualbox --virtualbox-hostonly-cidr 192.168.56.1/24 dev new adapter is created with different ip

I dont know if it is helpful. But in "dev" machine settings (in Virual box)
Settings -> Network -> Adapter 1 -> Attached to NAT is set

reinstalling Virtual Box / msysgit / deleting .docker foulder didn't help

[mattjanssen]

@cyclonebt How did you specify the already-existing adapter in the Vagrant config? I'm having the same issue and believe you solution will fix it.

Bring it up once with bridged networking, and it will show you the name of
the adapters when it asks you to select which one to use. Copy/paste the
name into the spec. Here's what mine looks like:

config.vm.network "public_network", bridge: "Realtek PCIe GBE Family
Controller", ip: "192.168.9.10"

On Wed, Jul 29, 2015 at 3:40 PM, Matt Janssen notifications@github.com
wrote:

@cyclonebt https://github.com/cyclonebt How did you specify the
already-existing adapter in the Vagrant config? I'm having the same issue
and believe you solution will fix it.

—
Reply to this email directly or view it on GitHub
#1521 (comment).

Scott Roberts, KB5TOR
http://ksstorm.info/_KSStorm.Info http://kstorm.info/ - Severe Storm
Outlooks, Safety Information and Video_

Follow Storm Chaser Scott Roberts:
http://facebook.com/chasersroberts http://twitter.com/KSStormInfo
http://plus.google.com/+KSStormInfo http://youtube.com/ksstormmedia

Video/Photo Licensing: (844) KS-STORM

[nathanleclaire]

Hi all, just some update on this:

I have reproduced the issue around VBoxManage hostonlyif create on Windows 10 and can confirm that command is failing.

I've made a comment on the Virtualbox ticket tracker here: https://www.virtualbox.org/ticket/14040

I can't really think of any way to work around it until upstream fixes this bug, so I'm all ears if anyone has suggestions.