I had similar issue and the reason was enabling Internet Connection Sharing or running a local DNS server.
There is another problem that has been blocking a couple of us, whereby there is no obvious error logged
The funny thing is that I had ICS already active when I installed the Docker for Windows for the first time, since one of my Hyper-V virtual switches was an external switch. I have removed it in the meantime and reinstalled Docker for Windows afterwards, still no joy 
.
@pflannery I had the same problem in a different context.
See my post, for the steps involved: Settings: Reset to default quits with Error [resolved] âŠ
-m
I am having the same problem 
tried uninstall, reinstall etc, still no luck
For me, it was Acrylic DNS Server.
âStop Acrylic Serviceâ solved my problem.
So thanks 
For me, removing all my other internal Hyper-V switch solved the issue.
1 Like
Had to uninstall D4W Beta 7, and install older version to overcome problem where VM couldnât get an IP addressâŠ
[21:57:01.635][Program ][Info ] Version: 1.10.6.958
[21:57:01.637][Program ][Info ] Starting on: 4/15/2016 9:57:01 PM
[21:57:01.639][Program ][Info ] Resources: C:\Program Files (x86)\Docker\Docker\Resources
[21:57:01.641][Program ][Info ] OS: Windows 10 Pro Insider Preview
[21:57:01.642][Program ][Info ] Edition: Professional
[21:57:01.644][Program ][Info ] Id: 1511
[21:57:01.646][Program ][Info ] Build: 14316
[21:57:01.648][Program ][Info ] BuildLabName: 14316.1000.amd64fre.rs1_release.160402-2217
Thx, removing all my other internal Hyper-V switches also solved issue with latest Beta 7 versionâŠ
[01:05:05.124][Program ][Info ] Version: Version 1.11.0-beta7 (build: 1692)
[01:05:05.127][Program ][Info ] Starting on: 4/16/2016 1:05:05 AM
[01:05:05.127][Program ][Info ] Resources: C:\Program Files\Docker\Docker\Resources
[01:05:05.127][Program ][Info ] OS: Windows 10 Pro
[01:05:05.127][Program ][Info ] Edition: Professional
[01:05:05.127][Program ][Info ] Id: 1511
[01:05:05.127][Program ][Info ] Build: 10586
[01:05:05.146][Program ][Info ] BuildLabName: 10586.212.amd64fre.th2_release_sec.160328-1908
Glad to hear that the Beta7 solved the issue. We will look into setups with multiple internal switches
Ugh⊠I canât just remove my other HyperV virtual switches. Itâs the only way this machine can get to the appropriate VLAN on my network. (Drivers are broken and wonât do VLAN, seriously.)
I can confirm that deleting the other internal switch(s) fixed the issue. I had an internal switch for the Windows Phone Emulator VM (Windows Phone Emulator Internal Switch). I deleted the MobyLinuxVM and the DockerNAT switch and while the other internal switch was in place I ran the following and got the error you see listedâŠ
//
PS C:\Program Files\Docker\Docker\resources> .\MobyLinux.ps1 -IsoFile .\mobylinux.iso -Create
Enabled workaround for Build 10586 VMSwitch issue
Creating Switch: DockerNATâŠ
New-NetIPAddress : Instance MSFT_NetIPAddress already exists
At C:\Program Files\Docker\Docker\resources\MobyLinux.ps1:140 char:32
-
$netIP = $networkAdapter | New-NetIPAddress -AddressFamily IPv4 ` -
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~- CategoryInfo : InvalidArgument: (MSFT_NetIPAddress:ROOT/StandardCimv2/MSFT_NetIPAddress) [New-NetIPAddress], CimException
- FullyQualifiedErrorId : Windows System Error 87,New-NetIPAddress
Switch created.
Using existing Net NAT: DockerNAT
Creading dynamic VHD: C:\Use
//
Notice the âInstance MSFT_NetIPAddress already existsâ error above.
After getting that error the VM and switch looked fine but Docker could not run because of the âunable to get IPâ error. So I deleted the Windows Phone Emulator switch and reran the command as listed below and now everything is working.
PS C:\Program Files\Docker\Docker\resources> .\MobyLinux.ps1 -IsoFile .\mobylinux.iso -Create
Enabled workaround for Build 10586 VMSwitch issue
Creating Switch: DockerNATâŠ
Switch created.
Using existing Net NAT: DockerNAT
Creading dynamic VHD: C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks\MobyLinuxVM.vhdx
Creating VM MobyLinuxVMâŠ
VM created.
PS C:\Program Files\Docker\Docker\resources>
Please let me know if there is any more data / testing / feedback I can give or do.
Thanks,
Jeff
I can not start VM too.
Here is my logs:
[23:42:20.699][Program ][Info ] Version: Version 1.11.0-beta7 (build: 1692)
[23:42:20.714][Program ][Info ] Starting on: 2016-04-19 11:42:20 PM
[23:42:20.714][Program ][Info ] Resources: C:\Program Files\Docker\Docker\Resources
[23:42:20.714][Program ][Info ] OS: Windows 10 Pro
[23:42:20.714][Program ][Info ] Edition: Professional
[23:42:20.730][Program ][Info ] Id: 1511
[23:42:20.730][Program ][Info ] Build: 10586
[23:42:20.730][Program ][Info ] BuildLabName: 10586.212.amd64fre.th2_release_sec.160328-1908
[23:42:20.730][Program ][Info ] Id: f8eefa09-1945-4b91-bbdd-5600ec3c85aa
[23:42:20.745][Program ][Info ] Sha1: 8b45bc3afc0ca2363890032ac63b003d80ccc242
[23:42:20.745][Program ][Info ] You can send feedback, including this log file, at https://forums.docker.com/c/docker-for-windows
[23:42:21.011][HyperV ][Info ] Checking for Hyper-V Windows optional feature
[23:42:21.152][PowerShell ][Info ] Run script...
[23:42:30.651][HyperV ][Info ] Hyper-V Windows feature is enabled
[23:42:32.090][Authentication ][Info ] Checking token
[23:42:32.605][Authentication ][Info ] Token is valid
[23:42:32.621][Auth ][Info ] null credential
[23:42:32.637][Auth ][Info ] Invalid credentials retrieved
[23:42:32.637][Firewall ][Info ] Opening TCP ports on the firewall for C:\Program Files\Docker\Docker\Resources\com.docker.proxy.exe...
[23:42:32.652][PowerShell ][Info ] Run script...
[23:42:33.355][Updater ][Info ] Checking for updates on the Beta channel...
[23:42:34.714][Updater ][Info ] Found remote version. Version = 1.11.0.1692
[23:42:34.714][Updater ][Info ] Local version is up to date.
[23:42:34.714][Updater ][Info ] Check for update done.
[23:42:38.152][Firewall ][Info ] Ports opened
[23:42:38.152][Firewall ][Info ] Opening UDP ports on the firewall for C:\Program Files\Docker\Docker\Resources\com.docker.proxy.exe...
[23:42:38.152][PowerShell ][Info ] Run script...
[23:42:39.699][Firewall ][Info ] Ports opened
[23:42:39.699][HyperV ][Info ] Creating a virtual machine named MobyLinuxVM
[23:42:39.715][HyperV ][Info ] Checking for Hyper-V Windows optional feature
[23:42:39.715][PowerShell ][Info ] Run script...
[23:42:40.184][HyperV ][Info ] Hyper-V Windows feature is enabled
[23:42:40.199][PowerShell ][Info ] Run script with parameters: -Create True -IsoFile C:\Program Files\Docker\Docker\Resources\mobylinux.iso...
[23:42:44.511][HyperV ][Info ] Using existing Switch: DockerNAT
[23:42:44.824][HyperV ][Info ] Using existing: MobyLinuxVM
[23:42:44.839][Proxy ][Info ] Starting com.docker.proxy
[23:42:44.949][HyperV ][Info ] Start a virtual machine named MobyLinuxVM
[23:42:44.949][HyperV ][Info ] Checking for Hyper-V Windows optional feature
[23:42:44.949][PowerShell ][Info ] Run script...
[23:42:45.027][Proxy ][Info ] 2016/04/19 23:42:45 dhcp server: ready
[23:42:45.043][Proxy ][Info ] 2016/04/19 23:42:45 poison pill: ready
[23:42:45.043][Proxy ][Info ] 2016/04/19 23:42:45 docker proxy: ready
[23:42:45.043][Proxy ][Info ] 2016/04/19 23:42:45 dns server: ready
[23:42:45.043][Proxy ][Info ] 2016/04/19 23:42:45 docker proxy (on deprecated port): ready
[23:42:45.417][HyperV ][Info ] Hyper-V Windows feature is enabled
[23:42:45.420][PowerShell ][Info ] Run script with parameters: -Start True...
[23:42:47.440][HyperV ][Info ] Removing com.docker.proxy firewall rules...
[23:42:48.266][HyperV ][Info ] Starting VM MobyLinuxVM...
[23:42:51.455][Notifications ][Error ] Error: Failed to start VM "MobyLinuxVM": 'MobyLinuxVM' failed to start.
Failed to start the virtual machine 'MobyLinuxVM' because one of the Hyper-V components is not running.
'MobyLinuxVM' failed to start. (Virtual machine ID 02F44872-5F8B-4A87-A62B-C44E747A8A88)
The Virtual Machine Management Service failed to start the virtual machine 'MobyLinuxVM' because one of the Hyper-V components is not running (Virtual machine ID 02F44872-5F8B-4A87-A62B-C44E747A8A88).
[23:42:54.421][Program ][Info ] Sending Bugsnag report 48ef2400-1bca-4363-9d11-fa6b2427bd6a ...
[23:42:55.682][Program ][Info ] Bugsnag report sent```Thank you very much! After upgrading to the latest beta this happened to me, and I had the same issue.
Regards Albert
This also solved the problem I was facing. Removing all internal Hyper-v except the Docker owned is the way to go
i re-install my win10, and nothing in HyperV.
but, that is happened,
because one of the Hyper-V components is not running
i want to know what component is not running.
I also had this problem but once I removed my other internal hyper-v switches it worked fine.
Docker Version 1.11.0-beta8 (build: 1832)
Windows 10 Pro Version 1511 Build 10586.218
The problem that I have now is that if I have Docker running, I am unable to bring up my Visual Studio Emulator for Android. It creates the Windows Phone Emulator Internal Switch and the Windows Phone Emulator VM but it never completely boots. If I shutdown Docker then I can use my emulator but I canât restart Docker because of the second internal switch.
Hi,
I have the same issue with the beta 8 (logs could be found here : http://pastebin.com/Zr0Wfyv4). And on hyper-v, the virtual machine does not have an assigned IP.
I have checked the following elements
- Internet Connection Sharing is disable
- Only the Docker NAT virtual switch exists
- Run netstat -abo : no other process uses the UDP Port 53
- Uninstall / Reinstall docker
I canât find a way to solve this issue 
Hi,
I had the same problem and i fixed it by doing:
- Right click in the whale icon.
- Settings
- Reset to factory defaultsâŠ
It is working now!
2 Likes
Thanks! reset to factory default works for me too