Docker not starting on W10 Insider Preview 17063

[tdroenner]

Expected behavior

Docker starts as usual.

Actual behavior

Unable to create File System Image
bei Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs:Zeile 36.
bei Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:Zeile 95.
bei Docker.Actions.<>c__DisplayClass18_0.b__0() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:Zeile 81.
bei Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:Zeile 59.

Information

Diagnostic-ID:
46919F58-4A29-4D8C-AC41-0CD2C20AF914/2017-12-23_00-07-31
Version 17.12.0-ce-rc4-win44 (14896)
Channel: edge
f23de3e
W10 Insider Preview 17063

Steps to reproduce the behavior

1. Upgade to 17063 Insider Preview and launch Docker for Windows

[tdroenner]

Still present with latest Edge release:
Unable to create File System Image
bei Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs:Zeile 36.
bei Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:Zeile 95.
bei Docker.Actions.<>c__DisplayClass20_0.b__0() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:Zeile 154.
bei Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:Zeile 59.

[nstrelow]

Please fix this. We need this. Is there no workaround?
I want to use Linux containers on Windows.

[Kevinrob]

My workaround is to rollback to previous Windows version. Just WOW how it's easy now 👍 (17046).
And Docker work again.

[misenhower]

I ran into this issue on today's update to the stable channel (version 17.12.0-ce-win46 2018-01-09). The previous stable channel version (17.09.1-ce-win42 2017-12-11) was working properly under 17063.

I was able to fix this by downgrading to the 17.09.1 release. For anyone else looking for the previous version's installer, you can find it here.

You'll have to manually uninstall the newer version of Docker first, but after installing the older version things are working again for me for now. (Of course this release doesn't have LCOW or anything else from the newer edge builds.)

Also, I found another reference to the "Unable to create File System Image" issue here, not sure if that's related.

[tdroenner]

I can confirm that a downgrade to Docker 17.09.1 is working.

[ztolley]

Another here with same issue

[djensen47]

18 days with no resolution? So angry and sad.

[djensen47]

@tdroenner Where did you find the older version of Docker??

[djensen47]

I can also confirm that 17.09.1 is working.

Here's a link to 17.09.1: https://download.docker.com/win/stable/14687/Docker%20for%20Windows%20Installer.exe

[aaronpowell]

Seems like the problem isn't with Docker, but Windows itself - moby/moby#35854

I foolishly updated to the latest stable as well so it looks like I'll have to downgrade and keep an eye on update prompt :(.

[allenstecat]

I will see what I can find out internally about this. I am going to test upgrading to a canary windows build to see if that fixes this as well.

[jasonbivins]

Windows 17063 did break a few things for Docker - but it's expected to be fixed in the next insider release
https://blogs.windows.com/windowsexperience/2017/12/19/announcing-windows-10-insider-preview-build-17063-pc/#8u4SZFHchBmH2swz.97

[marfillaster]

If you're on 17.09.1 on Windows Insider 17074, skip 17.12.0-ce-win47

[dannyk81]

Windows Insider Build 17074 released, but seems like the issue is still there.

I did a test anyway and can confirm that at least for me the issue is still there.