Docker won't start on win10 1803 #1927

zersiax · 2018-04-08T12:38:48Z

[x ] I have tried with the latest version of my channel (Stable or Edge)
[x ] I have submitted Diagnostics
[x ] I have included the Diagnostics ID in this Issue
Windows Version: Windows 10 1803
Docker for Windows Version: 18.03

Expected behavior

Docker daemon starts normally

Actual behavior

Docker attempts to start, but crashes with the error described in attached log file.

Information

Diagnostics ID: 7307E659-4128-4582-AE1B-B34005A9990E/2018-04-08_14-26-28
Windows version: Windows 10 1803, build 17133.1

Steps to reproduce the behavior

Upgrade windows 10 1803 from home to professional using a product key.
Reboot.
Install Docker for Windows, either Stable or Edge give the same results.
Restart again.
Docker tries to start, but errors.
switch to Windows Containers. This works fine.
Switch back to Linux containers. This errors in a similar way to just trying to start, resulting in you getting stuck on Windows Containers.
Uninstall Docker for Windows, remove %appdata%\locale and \roaming Docker folders, as well as userdir.docker.
Disable both HyperV and Containers from the "Turn Windows Features on and off" dialog.
Reboot, re-enable them. Reboot again.
In an elevated powershell command, run commands to enable hyperv and containers with the -all switch just for some added certainty.
Reinstall Docker.
Reboot.
Docker starts, once again in Linux Container mode ....and fails.
Pull hair out in frustration, grab your nearest container of strong liquor and give up.

I need this to work for my job, is there anyone over here who can see why this isn't working as advertised? I know very little about Docker and even less about HyperV, so I don't really have the know-how to debug this any further and I've already spent half my sunday on this to not have to spend hours doing this when I'm trying to actually get work done.
docker_log.txt

PascalKu · 2018-04-08T14:36:03Z

Same issue here.

nalpr · 2018-04-10T21:04:58Z

1- I removed docker, disabled hyper-v , removed dockerNat adapter.
2- restarted windows .
3- reinstalled docker
4- enabled hyper-v. restarted windows

solved
I hope the best for you, been in same situation after update.

ioagadmin · 2018-05-15T04:30:38Z

I am about to update to v1803, is that 100% broken cause with Docker?

jenslaufer · 2018-05-15T11:40:06Z

Could not get docker working with v1803...downgraded to v1709

Drumstix42 · 2018-05-21T18:05:07Z

Can confirm, this is a problem with upgrading to 1803. However, not all setups seem to run into the issue.

I followed @nalpr 's instructions exactly, and it got me back up and running. Thanks!

Edit Side note, I'm using version 17.12.0-ce-win47 because the latest version gives problems with a project. Haven't tested latest version 18 and upgraded Windows from v1709 to v1803. I'm not able to test this scenario.

r3dius · 2018-06-04T13:49:59Z

@nalpr , thank you for this instructions. It deblocked my situation but can be embarassing when we have many packages to download.:/....

nalpr · 2018-06-05T09:18:22Z

@r3dius @Drumstix42 this happened again after another update.

I deleted all the hyper-v network adapters in device manager. solved the problem. without restarting or anything.

ctgarvey · 2018-06-11T22:12:25Z

I can get the basic plain vanilla microsoft/iis image to spin up as a docker (18.03.01) windows container in Windows 10 enterprise 1803 but cannot access it via a mapped port on the host. Netstat -a reports the port state as SYN_SENT . ie no response from the server. I can access it on port 80. Theres something broken re the networking. I can see the website only if i use the original http TCP 80 port, and not the mapped port (8000, as per the example) .Any suggestions on how to fix the broken port mapping? appreciated :-)

pessimism · 2018-08-02T23:04:01Z

Removing all Hyper-V Network adapters also worked for me without a restart. Thank you @nalpr

pessimism · 2018-08-02T23:08:45Z

.. spoke too soon. still only linux containers

pessimism · 2018-08-03T00:59:28Z

@nalpr s 4 step fix worked for me. though when removing one of my hyper-v virtual switches i also encountered this obstacle removing it https://superuser.com/questions/1192492/how-to-remove-a-hyper-v-virtual-ethernet-switch the solution there fixed that issue

jycr · 2018-09-18T22:06:11Z

We faced a similar problem with Windows 10 (build 1803) :

Échec de l’accès au magasin de configuration : Impossible de trouver un fournisseur de prise en charge de disque virtuel pour le fichier spécifié. (0xC03A0014).
à New-MobyLinuxVM, <Aucun fichier> : ligne 187
à <ScriptBlock>, <Aucun fichier> : ligne 394
   à Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters) dans C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs:ligne 36
   à Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) dans C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:ligne 77
   à Docker.Actions.<>c__DisplayClass16_0.<Start>b__0() dans C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:ligne 61
   à Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1() dans C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:ligne 59

After diagnosing the Windows 10 environment, we noticed a problem with a driver called Microsoft_VHD_ISO_VHBA_01:

After updating the driver and restarting Docker, everything seems to be fixed.

AnthonyCoughlin · 2018-11-11T01:48:13Z

Hey All,

Not sure if this is related, but I ran into a similar issue where Docker-Machine would not load and deleting the Virtualbox adapter from the device manager fixed the issue.

Thanks for the help,
AnthonyC

SetTrend · 2018-12-21T03:04:42Z

Same issue here.

Today I set-up a fresh Windows 10x64 1809 VM, installed Docker for Windows (latest, of course) and can't get the Linux container up running:

Switching to Windows containers works flawlessly, but switching back to the Linux container doesn't work.

Here's an excerpt of the Docker for Windows log:

[03:57:54.940][HyperV         ][Info   ] Remove existing DVDs
[03:57:55.191][HyperV         ][Info   ] Attach DVD C:\Program Files\Docker\Docker\Resources\docker-for-win.iso
[03:57:55.315][HyperV         ][Info   ] Attach Config ISO C:\ProgramData\DockerDesktop\tmp-d4w\config.iso
[03:57:56.011][HyperV         ][Info   ] Attach Docker ISO C:\Program Files\Docker\Docker\Resources\docker.iso
[03:57:57.535][HyperV         ][Debug  ] [start] took 00:00:03.1105924 to run
[03:57:58.452][Moby           ][Info   ] Connected
[03:57:58.468][Moby           ][Info   ] [    0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[03:57:58.483][Moby           ][Info   ] [    0.000000] setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:128 nr_node_ids:1
[03:57:58.497][Moby           ][Info   ] [    0.000000] percpu: Embedded 36 pages/cpu @ffff8821fac00000 s107096 r8192 d32168 u262144
[03:57:58.497][Moby           ][Info   ] [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 514505
[03:57:58.528][Moby           ][Info   ] [    0.000000] Kernel command line: BOOT_IMAGE=/boot/kernel console=ttyS0 page_poison=1 vsyscall=emulate panic=1 root=/dev/sr0 text
[03:57:58.544][Moby           ][Info   ] [    0.000000] log_buf_len individual max cpu contribution: 4096 bytes
[03:57:58.560][Moby           ][Info   ] [    0.000000] log_buf_len total cpu_extra contributions: 520192 bytes
[03:57:58.560][Moby           ][Info   ] [    0.000000] log_buf_len min size: 131072 bytes
[03:57:58.575][Moby           ][Info   ] [    0.000000] log_buf_len: 1048576 bytes
[03:57:58.575][Moby           ][Info   ] [    0.000000] early log buf free: 122996(93%)
[03:57:58.591][Moby           ][Info   ] [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[03:57:58.607][Moby           ][Info   ] [    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[03:57:58.622][Moby           ][Info   ] [    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[03:57:58.638][Moby           ][Info   ] [    0.000000] Memory: 2008100K/2096168K available (8113K kernel code, 1393K rwdata, 2708K rodata, 1404K init, 564K bss, 88068K reserved, 0K cma-reserved)
[03:57:58.653][Moby           ][Info   ] [    0.000000] Kernel/User page tables isolation: enabled
[03:57:58.653][Moby           ][Info   ] [    0.000000] Hierarchical RCU implementation.
[03:57:58.670][Moby           ][Info   ] [    0.000000] 	Build-time adjustment of leaf fanout to 64.
[03:57:58.684][Moby           ][Info   ] [    0.000000] Using NULL legacy PIC
[03:57:58.700][Moby           ][Info   ] [    0.000000] NR_IRQS:8448 nr_irqs:1448 0
[03:57:58.700][Moby           ][Info   ] [    0.000000] Console: colour dummy device 80x25
[03:57:58.716][Moby           ][Info   ] [    0.000000] console [ttyS0] enabled
[03:57:58.731][Moby           ][Info   ] [    0.000000] allocated 4194304 bytes of page_ext
[03:57:58.747][Moby           ][Info   ] [    0.000000] tsc: Unable to calibrate against PIT
[03:57:58.747][Moby           ][Info   ] [    0.000000] tsc: HPET/PMTIMER calibration failed
[03:59:58.826][NamedPipeClient][Error  ] Unable to send Start: No activity detected on VM, aborting

I can't even access the Linux VM using Hyper-V Manager directly:

The error message displayed by Hyper-V Manager is: "Video Remoting was disconnected".

Probably a duplicate of #267.

docker-robott · 2019-03-21T02:00:35Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

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

SetTrend · 2019-03-21T02:19:55Z

/remove-lifecycle stale

docker-robott · 2019-06-19T01:00:19Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

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

SetTrend · 2019-06-19T22:15:27Z

/remove-lifecycle stale

docker-robott · 2019-09-17T01:00:16Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

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

jbjhjm · 2020-05-19T09:15:23Z

/remove-lifecycle stale

jbjhjm · 2020-05-19T09:15:38Z

/lifecycle frozen

jbjhjm · 2020-05-19T09:21:50Z

Problem still exists. Trying to reinstall Docker Desktop 2.3.0.2 because it crashed and reset to factory settings failed, too.
Uninstall has frozen. Reinstall fails as docker.iso / docker-desktop.iso cannot be deleted. Tried everything above, disabled hyper-v and its networks and devices. No success.
I'm now going to test to remove the files in safe mode.
ANNOYING, I must say.
Seeing dozens of issue threads open for years (or auto-closed) the docker team should really take action :/

Edit:
For anyone looking for help, these are the steps that worked for me:

Run uninstaller
Run PS Script found here https://success.docker.com/article/how-to-completely-remove-docker-in-windows-10
Check if C:\Program Files\Docker\ still contains files, if not everything is fine
Disable Hyper-V Windows Feature
Boot into safe mode or take ownership of left files (command: Can't remove C:\ProgramData\Docker after uninstalling Docker #1544 (comment))
Delete them
Re-enable Hyper-V Win Feature
Install Docker again

docker-robott · 2020-06-27T03:14:24Z

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

docker-robott added the version/18.03.0-ce-win59 label Apr 8, 2018

docker-robott added the lifecycle/stale label Mar 21, 2019

docker-robott removed the lifecycle/stale label Mar 21, 2019

docker-robott added the lifecycle/stale label Jun 19, 2019

docker-robott removed the lifecycle/stale label Jun 19, 2019

docker-robott added the lifecycle/stale label Sep 17, 2019

docker-robott closed this as completed Oct 17, 2019

LeonardAB mentioned this issue Dec 10, 2019

Docker stopped working after upgrading to Windows 10 1803 Initial Response #3554

Closed

docker-robott removed the lifecycle/stale label May 19, 2020

docker-robott added the lifecycle/frozen label May 19, 2020

docker-robott added the lifecycle/locked label Jun 27, 2020

docker locked and limited conversation to collaborators Jun 27, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Docker won't start on win10 1803 #1927

Docker won't start on win10 1803 #1927

zersiax commented Apr 8, 2018

PascalKu commented Apr 8, 2018

nalpr commented Apr 10, 2018

ioagadmin commented May 15, 2018

jenslaufer commented May 15, 2018

Drumstix42 commented May 21, 2018 •

edited

Loading

r3dius commented Jun 4, 2018

nalpr commented Jun 5, 2018

ctgarvey commented Jun 11, 2018

pessimism commented Aug 2, 2018 •

edited

Loading

pessimism commented Aug 2, 2018

pessimism commented Aug 3, 2018

jycr commented Sep 18, 2018

AnthonyCoughlin commented Nov 11, 2018

SetTrend commented Dec 21, 2018 •

edited

Loading

docker-robott commented Mar 21, 2019

SetTrend commented Mar 21, 2019

docker-robott commented Jun 19, 2019

SetTrend commented Jun 19, 2019

docker-robott commented Sep 17, 2019

jbjhjm commented May 19, 2020

jbjhjm commented May 19, 2020

jbjhjm commented May 19, 2020 •

edited

Loading

docker-robott commented Jun 27, 2020

Docker won't start on win10 1803 #1927

Docker won't start on win10 1803 #1927

Comments

zersiax commented Apr 8, 2018

Expected behavior

Actual behavior

Information

Steps to reproduce the behavior

PascalKu commented Apr 8, 2018

nalpr commented Apr 10, 2018

ioagadmin commented May 15, 2018

jenslaufer commented May 15, 2018

Drumstix42 commented May 21, 2018 • edited Loading

r3dius commented Jun 4, 2018

nalpr commented Jun 5, 2018

ctgarvey commented Jun 11, 2018

pessimism commented Aug 2, 2018 • edited Loading

pessimism commented Aug 2, 2018

pessimism commented Aug 3, 2018

jycr commented Sep 18, 2018

AnthonyCoughlin commented Nov 11, 2018

SetTrend commented Dec 21, 2018 • edited Loading

Same issue here.

Here's an excerpt of the Docker for Windows log:

I can't even access the Linux VM using Hyper-V Manager directly:

docker-robott commented Mar 21, 2019

SetTrend commented Mar 21, 2019

docker-robott commented Jun 19, 2019

SetTrend commented Jun 19, 2019

docker-robott commented Sep 17, 2019

jbjhjm commented May 19, 2020

jbjhjm commented May 19, 2020

jbjhjm commented May 19, 2020 • edited Loading

docker-robott commented Jun 27, 2020

Drumstix42 commented May 21, 2018 •

edited

Loading

pessimism commented Aug 2, 2018 •

edited

Loading

SetTrend commented Dec 21, 2018 •

edited

Loading

jbjhjm commented May 19, 2020 •

edited

Loading