Docker unable to start on Windows 10

[Getitdan]

• I have tried with the latest version of my channel (Stable or Edge)
• I have uploaded Diagnostics
• Diagnostics ID: C345D429-0AF6-4E57-94DB-8A99E4B6BF7F/2018-07-16_14-48-06

Expected behavior

Docker should run on windows 10.

Actual behavior

Docker does not start.

Information

• Windows Version: 10
• Docker for Windows Version: 18.03.1-ce-win65 (17513)
• I have a new Windows 10 pro (upgraded from Windows 7).
  After a fresh installation of Docker for Windows, I am getting the error:
  
  The text in the error above:

Unable to start: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: 'MobyLinuxVM' failed to start. (Virtual machine ID 1D60AE71-F625-4A14-95D6-264618532954)
at Start-MobyLinuxVM, : line 300
at , : line 395
at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs:line 36
at Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 67
at Docker.Actions.<>c__DisplayClass14_0.b__0() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 51
at Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59

Also, the log.txt file includes the following errors:

...
[14:12:09.685][Moby ][Error ] Failed to read Moby's logs: The operation has timed out.
...
[14:12:13.257][VpnKit ][Error ] vpnkit.exe: While watching /etc/resolv.conf: ENOENT
...
[14:12:45.643][Linux ][Error ] Failed to start: Unable to start: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: 'MobyLinuxVM' failed to start. (Virtual machine ID D4AE07B1-7A05-439E-A17D-F6572AE861DF)
at Start-MobyLinuxVM, : line 300
at , : line 395. Let's retry

What have I tried
This happens all over again (even after a full uninstalling & installing).
The docker icon in tray is red. I tried the following command (as suggested by: #587):
netsh interface ipv4 set address name="vEthernet (DockerNAT)" static 10.0.75.1 255.255.255.0
This made docker tray icon to go white ("Docker is running" status), instead of red, pretending to work. But... now, running "docker ps" results in the following error:

error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.37/containers/json: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.

I tried running: "netcfg -d", as suggested by #748. But this didn't solve the issue.

I have also tried to disable hyper-v, and let docker to start it. Still didn't work.

This is really frustrating, as I cannot use Docker at all.
I made an upgrade to my Windows, from 7 to 10, only to get Docker running.
But all I'm getting are problems. Why isn't the normal installation simply work?
Thanks!

Steps to reproduce the behavior

1. Just try to install docker on Windows 10 (potentially to occur on an upgraded Windows 7).

[bogere]

I was also struggling to start docker after installation...
You should try installing the window Updates. the latest before you start running your docker.
I did this and it worked perfectly. now iam able to run the docker commands . try that first

[Getitdan]

@bogere Thanks for your input. My Windows is already fully updated:

I did nothing wrong, and docker won't work. Please help me.

[rn]

@Getitdan do you run any AV software by any chance? Have you tried a factory reset?

[Getitdan]

@rn I have just disabled my Nod32 Antivirus, and reinstalled docker. But sadly, the same problem occurs.

I upgraded my Windows 7 to Windows 10. Do you have any other suggestion, or should I format my whole pc? (if this what you mean by factory reset). Thanks a lot for your response! It's really important for me.

Update: usually docker is not running. But sometimes, after a "Restart" option inside docker, it is suddenly shown as running. Then, I try to run simple commands and get errors.

For example, running:
docker build -t test .
results in:

ERRO[0000] failed to dial gRPC: cannot connect to the Docker daemon. Is 'docker daemon' running on this host?: open //./pipe/docker_engine: The system cannot find the file specified.
error during connect: Post http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.37/build?buildargs=%7B%7D&cachefrom=%5B%5D&cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile&labels=%7B%7D&memory=0&memswap=0&networkmode=default&rm=1&session=48f16b2071a78c796b48c823bec780a64f4e968b6285522fa06743b4a3751e42&shmsize=0&t=test&target=&ulimits=null: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.

And:
docker ps
shows:

error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.37/containers/json: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.

[Getitdan]

Update:
I've tried this command:
docker-machine create default
and got:

Running pre-create checks...
Error with pre-create check: "This computer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is activated. Either use Hyper-V as a driver, or disable the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)"

Running:
docker-machine create -d virtualbox --virtualbox-no-vtx-check test
shows:

Running pre-create checks...
Creating machine...
(test) Copying C:\Users\user.docker\machine\cache\boot2docker.iso to C:\Users\user.docker\machine\machines\test\boot2docker.iso...
(test) Creating VirtualBox VM...
(test) Creating SSH key...
(test) Starting the VM...
(test) Check network to re-create if needed...
(test) Windows might ask for the permission to create a network adapter. Sometimes, such confirmation window is minimized in the taskbar.
(test) Creating a new host-only adapter produced an error: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe hostonlyif create failed:
(test) 0%...
(test) Progress state: E_INVALIDARG
(test) VBoxManage.exe: error: Failed to create the host-only adapter
(test) VBoxManage.exe: error: Assertion failed: [!aInterfaceName.isEmpty()] at 'F:\tinderbox\win-5.2\src\VBox\Main\src-server\HostNetworkInterfaceImpl.cpp' (76) in long __cdecl HostNetworkInterface::init(class com::Bstr,class com::Bstr,class com::Guid,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0038).
(test) VBoxManage.exe: error: Please contact the product vendor!
(test) VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
(test) VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 94 of file VBoxManageHostonly.cpp
(test)
(test) This is a known VirtualBox bug. Let's try to recover anyway...
(test) Found a new host-only adapter: "VirtualBox Host-Only Ethernet Adapter #10"
(test) Windows might ask for the permission to configure a network adapter. Sometimes, such confirmation window is minimized in the taskbar.
(test) Windows might ask for the permission to configure a dhcp server. Sometimes, such confirmation window is minimized in the taskbar.
Error creating machine: Error in driver during machine creation: Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm test --type headless failed:
VBoxManage.exe: error: Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
Details: 00:00:02.466419 Power up failed (vrc=VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT, rc=E_FAIL (0X80004005))

Now, I disabled hyper-v, reinstalled docker, made a reset, and run:
docker-machine create default

Now I get:

Running pre-create checks...
Creating machine...
(default) Copying C:\Users\user.docker\machine\cache\boot2docker.iso to C:\Users\user.docker\machine\machines\default\boot2docker.iso...
(default) Creating VirtualBox VM...
(default) Creating SSH key...
(default) Starting the VM...
(default) Check network to re-create if needed...
(default) Windows might ask for the permission to create a network adapter. Sometimes, such confirmation window is minimized in the taskbar.
(default) Creating a new host-only adapter produced an error: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe hostonlyif create failed:
(default) 0%...
(default) Progress state: E_INVALIDARG
(default) VBoxManage.exe: error: Failed to create the host-only adapter
(default) VBoxManage.exe: error: Assertion failed: [!aInterfaceName.isEmpty()] at 'F:\tinderbox\win-5.2\src\VBox\Main\src-server\HostNetworkInterfaceImpl.cpp' (76) in long __cdecl HostNetworkInterface::init(class com::Bstr,class com::Bstr,class com::Guid,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0038).
(default) VBoxManage.exe: error: Please contact the product vendor!
(default) VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
(default) VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 94 of file VBoxManageHostonly.cpp
(default)
(default) This is a known VirtualBox bug. Let's try to recover anyway...
(default) Found a new host-only adapter: "VirtualBox Host-Only Ethernet Adapter #11"
(default) Windows might ask for the permission to configure a network adapter. Sometimes, such confirmation window is minimized in the taskbar.
(default) Windows might ask for the permission to configure a dhcp server. Sometimes, such confirmation window is minimized in the taskbar.
(default) Waiting for an IP...
(default) The host-only adapter is corrupted. Let's stop the VM, fix the host-only adapter and restart the VM
(default) Windows might ask for the permission to configure a network adapter. Sometimes, such confirmation window is minimized in the taskbar.
(default) Waiting for an IP...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with boot2docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: docker-machine env default

But docker is red.

Bottom line: nothing works. I've tried everything. Hope someone can help.

[Getitdan]

@rn Thanks, I formatted my whole Windows, and now it works.

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked