Unable to run Docker for Windows on Windows 10 Ent #74

nijel91 · 2016-09-10T03:47:07Z

Expected behavior

Ability to run Docker for Windows

Actual behavior

Docker Daemon not starting

Information

Diagnostic ID: 0FE9B5A9-AEF2-4210-BE1E-FFEAAFAD5A37/2016-09-09_22-42-17
host distribution and version: Windows 10 Enterprise 10.0.10586

Steps to reproduce the behavior

to reproduce, please follow installation instructions

dgageot · 2016-09-16T16:53:48Z

Hi @nijel91 thank you for reporting this issue! Can you please update to 1.12.1-stable or beta26 and tell us if the issue is fixed for you now?

danbeaulieu · 2016-09-16T17:53:29Z

I was also having issues on Windows 10 Enterprise on several different hosts.

I just installed Docker for Windows Beta 26 and it was still not able to start, crash report:
0199DC35-2724-4E6E-B6BC-28BDF9573BF9/2016-09-16_13-52-02

Unable to write to the database. Exit code: 1
   at Docker.Backend.Database.WriteKeys(ICollection`1 keyValues)
   at Docker.Backend.Database.ModifyDatabase(ICollection`1 keyValuesToWrite, ICollection`1 keysToRemove)
   at Docker.Backend.Database.Write(Settings settings)
   at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings)
   at Docker.Backend.ContainerEngine.Linux.Start(Settings settings)
   at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass8_0.<Register>b__0(Object[] parameters)
   at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)

Gmanweb · 2016-09-25T16:13:49Z

same problem trying to start docker on windows, fresh install.
version

C:\gman>docker --version
Docker version 1.12.1, build 23cf638

ERROR:

Unable to write to the database. Exit code: 1
   at Docker.Backend.Database.WriteKeys(ICollection`1 keyValues)
   at Docker.Backend.Database.ModifyDatabase(ICollection`1 keyValuesToWrite, ICollection`1 keysToRemove)
   at Docker.Backend.Database.Write(Settings settings)
   at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings)
   at Docker.Backend.ContainerEngine.Linux.Start(Settings settings)
   at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass8_0.<Register>b__0(Object[] parameters)
   at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)

AndyBerman · 2016-09-26T14:10:54Z

I'm having the same problem. Have tried uninstalling & reinstalling both Docker and Hyper-V.

cgatian · 2016-09-28T18:48:20Z

Any resolution to this?

cgatian · 2016-09-28T19:34:34Z

So in my situation, I had Docker automatically install Hyper-V. This completes without a hickup. However, if you uninstall Hyper-V and attempt to reinstall it you will see the installation is actually not allowed. Verify your CPU supports virtualization by performing opening task manager and verifying that Virtualization is enabled. If it's not shown, then it will not work.

AndyBerman · 2016-09-28T19:47:35Z

It shows Virtualization is Enabled.

friism · 2016-09-29T02:45:15Z

@cgatian is the screenshot you posted from another system than then one where you experienced the problem?

chrisella · 2016-09-29T07:53:03Z

Exactly the same problem here, it's particularly annoying as it happened for me once I just finished moving all of our build flow and tool-chain to containers, typical ha.
I don't know if it's relevant but I think it's failing coincided with a windows 10 update for me.

Seems to be when it's trying to copy over the certificates possibly:

... Here is ~ 20,000 lines of certificates in the log then finally at the end ...
-----END CERTIFICATE-----
: The pipe has been ended.
2016/09/29 08:46:49 Failed to clunk fid 127
2016/09/29 08:46:49 Failed to write com.docker.driver.amd64-linux/etc/ssl/certs/ca-certificates.crt = C:\WINDOWS\TEMP\tmp29D2.tmp: 0x6d

[08:46:49.870][NamedPipeServer][Error ] Unable to execute Start: Unable to write to the database. Exit code: 1 at Docker.Backend.Database.WriteFile(String key, String file)
at Docker.Backend.Database.Write(Settings settings)
at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings)
at Docker.Backend.ContainerEngine.Linux.Start(Settings settings)
at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass8_0.b__0(Object[] parameters)
at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)

dev2see · 2016-09-30T15:57:07Z

The same problem

crutchfield · 2016-10-04T13:34:05Z

Appears to be same issue I am having as well. Tried stable and beta versions and got the same results. Errors appear in log right before attempting to read/write certificates. Be happy to provide more info to help isolate.

[09:12:41.534][DataKit ][Info ] +850368us fs9p [ERROR] dispatcher caught Unix.Unix_error(Unix.EPIPE, "bytes_read", ""): no more requests will be handled
[09:12:41.670][Database ][Info ] Successfully removed 3 value(s)
[09:12:41.685][DataKit ][Info ]
[09:12:41.685][DataKit ][Info ] +1001096us fs9p [ERROR] dispatcher caught Unix.Unix_error(Unix.EPIPE, "bytes_read", ""): no more requests will be handled
[09:12:41.748][Database ][Info ] Writing com.docker.driver.amd64-linux/etc/ssl/certs/ca-certificates.crt=C:\windows\TEMP\tmpE621.tmp
[09:12:47.400][Database ][Error ] 2016/10/04 09:12:41 fatal error reading msg: EOF

friism · 2016-10-04T13:47:02Z

@chrisella @crutchfield thanks for reporting, a fix is in the works!

chrisella · 2016-10-04T13:47:46Z

@friism Excellent great news! :)
thanks

danbeaulieu · 2016-10-04T13:53:37Z

@friism Are there 2 separate issues here? I do not see the log statements @crutchfield and @chrisella posted and the OP is a bit vague. Just wondering if we should have a separate issue if there is indeed a separate bug.

Latest diagnostic id: 816C0048-9BC7-4861-9DF8-0BEC0FEDE44F/2016-10-04_09-50-04

This is on Windows 10 Enterprise running 1.12.2-rc1-beta27.1

husainaloos · 2016-10-04T14:21:42Z

There might be two different problems here, with the same error message. I am trying to run beta version (tried the stable, same problem) on a windows 10 enterprise machine running inside VMware.

Unable to write to the database. Exit code: 1
   at Docker.Backend.Database.WriteKeys(ICollection`1 keyValues)
   at Docker.Backend.Database.ModifyDatabase(ICollection`1 keyValuesToWrite, ICollection`1 keysToRemove)
   at Docker.Backend.Database.Write(Settings settings)
   at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings)
   at Docker.Backend.ContainerEngine.Linux.Start(Settings settings)
   at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass8_0.<Register>b__0(Object[] parameters)
   at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)

The log

[09:19:24.157][Database       ][Error  ] Unable to modify database: Unable to write to the database. Exit code: 1. Let's retry in 1s
[09:19:25.162][Database       ][Info   ] Writing com.docker.driver.amd64-linux/net/config=static
[09:19:25.169][Database       ][Info   ] Writing com.docker.driver.amd64-linux/net/address=10.0.75.2
[09:19:25.178][Database       ][Info   ] Writing com.docker.driver.amd64-linux/net/netmask=255.255.255.0
[09:19:25.185][Database       ][Info   ] Writing com.docker.driver.amd64-linux/net/gateway=10.0.75.1
[09:19:25.190][Database       ][Info   ] Writing com.docker.driver.amd64-linux/network=hybrid
[09:19:25.193][Database       ][Info   ] Writing com.docker.driver.amd64-linux/etc/docker/daemon.json={"registry-mirrors":[],"insecure-registries":[],"debug":false}
[09:19:25.196][Database       ][Info   ] Writing com.docker.driver.amd64-linux/etc/sysctl.conf=
[09:19:25.200][Database       ][Info   ] Writing com.docker.driver.amd64-linux/native/port-forwarding=true
[09:19:25.204][Database       ][Info   ] Writing com.docker.driver.amd64-linux/proxy/exclude=
[09:19:25.208][Database       ][Info   ] Writing com.docker.driver.amd64-linux/proxy/http=http://autoproxy.gm.com/
[09:19:25.212][Database       ][Info   ] Writing com.docker.driver.amd64-linux/proxy/https=http://autoproxy.gm.com/
[09:19:26.256][Database       ][Error  ] 2016/10/04 09:19:25 Retry dialing \\.\pipe\dockerDataBase in 100ms
2016/10/04 09:19:25 Retry dialing \\.\pipe\dockerDataBase in 100ms
2016/10/04 09:19:25 Retry dialing \\.\pipe\dockerDataBase in 100ms
2016/10/04 09:19:25 Retry dialing \\.\pipe\dockerDataBase in 100ms
2016/10/04 09:19:25 Retry dialing \\.\pipe\dockerDataBase in 100ms
2016/10/04 09:19:25 Retry dialing \\.\pipe\dockerDataBase in 100ms
2016/10/04 09:19:25 Retry dialing \\.\pipe\dockerDataBase in 100ms
2016/10/04 09:19:25 Retry dialing \\.\pipe\dockerDataBase in 100ms
2016/10/04 09:19:26 Retry dialing \\.\pipe\dockerDataBase in 100ms
2016/10/04 09:19:26 Retry dialing \\.\pipe\dockerDataBase in 100ms
2016/10/04 09:19:26 Failed to contact the database on \\.\pipe\dockerDataBase: open \\.\pipe\dockerDataBase: The system cannot find the file specified.

[09:19:26.266][NamedPipeServer][Error  ] Unable to execute Start: Unable to write to the database. Exit code: 1    at Docker.Backend.Database.WriteKeys(ICollection`1 keyValues)
   at Docker.Backend.Database.ModifyDatabase(ICollection`1 keyValuesToWrite, ICollection`1 keysToRemove)
   at Docker.Backend.Database.Write(Settings settings)
   at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings)
   at Docker.Backend.ContainerEngine.Linux.Start(Settings settings)
   at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass8_0.<Register>b__0(Object[] parameters)
   at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)
[09:19:26.277][NamedPipeClient][Error  ] Unable to send Start: Unable to write to the database. Exit code: 1
[09:19:26.289][Notifications  ][Error  ] Unable to write to the database. Exit code: 1
[09:19:26.297][Program        ][Info   ] Sending Bugsnag report 68e2fdbf-8a4a-445f-be5f-bad11239dd73...
[09:19:27.157][Program        ][Info   ] Bugsnag report 68e2fdbf-8a4a-445f-be5f-bad11239dd73 sent
[09:19:27.188][NamedPipeClient][Info   ] Sending DownloadVmLogs()...
[09:19:27.195][NamedPipeServer][Info   ] DownloadVmLogs()
[09:19:27.199][PowerShell     ][Info   ] Run script...
[09:19:27.265][HyperV         ][Warning] Unable to download logs: 2016/10/04 09:19:27 Failed to Dial a04a4196-b656-4ddd-a01d-4666cb8409e4 445ba2cb-e69b-4912-8b42-d7f494d007ea : A socket operation encountered a dead network.

[09:19:27.272][NamedPipeServer][Info   ] DownloadVmLogs done.
[09:19:27.279][NamedPipeClient][Info   ] Received response for DownloadVmLogs
[09:20:18.992][ErrorReportWindow][Info   ] Open logs

danbeaulieu · 2016-10-13T19:15:17Z

This doesn't appear to be fixed on

Version: 1.12.2-beta28 (7813)
Channel: Beta
Sha1: b09fe3ddc04b65d8a6219f27132a10a7918b3a91

Current crash report 816C0048-9BC7-4861-9DF8-0BEC0FEDE44F/2016-10-13_15-11-07

srinathanand · 2016-10-14T18:52:03Z

Same problem on Windows 10 Version 1607 (OS Build 14393.321).

Docker version returns - docker --version
Docker version 1.12.1, build 23cf638

Hyper-V is enabled with a pop-up that came up when installing Docker and on restart this is the error -

Unable to write to the database. Exit code: 1
   at Docker.Backend.Database.WriteKeys(ICollection`1 keyValues)
   at Docker.Backend.Database.ModifyDatabase(ICollection`1 keyValuesToWrite, ICollection`1 keysToRemove)
   at Docker.Backend.Database.Write(Settings settings)
   at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings)
   at Docker.Backend.ContainerEngine.Linux.Start(Settings settings)
   at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass8_0.<Register>b__0(Object[] parameters)
   at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)

Crash report diagnostic id - 41EAEBF4-5972-49F7-9CDB-36E06570325D/2016-10-14_14-29-22

AndyBerman · 2016-10-14T19:00:59Z

Upgrading to the Beta Channel Version 1.12.2-beta28 (7813) resolved this problem for me.

srinathanand · 2016-10-14T19:32:28Z

Thanks @AndyBerman. I'll try that and post my results.

srinathanand · 2016-10-14T19:40:42Z

@AndyBerman -I downloaded the Beta installer and ran it but I am still seeing the same problem. Here is my Docker version -
docker --version
Docker version 1.12.2, build bb80604, experimental

chrisella · 2016-10-17T08:08:56Z

I've also installed the latest Beta version (1.12.2-beta28 (7813)) and am having the same issue persist with the failure to write to the database.
:(

UPDATE: Scratch that! after a few restarts, much finger crossing and some voodoo apparently it's now started working on that version I installed above.

srinathanand · 2016-10-17T12:27:49Z

@chrisella - where did you get the 1.12.2-beta28 (7813) from ?

chrisella · 2016-10-17T12:29:10Z

I downloaded the BETA channel here : https://docs.docker.com/docker-for-windows/

srinathanand · 2016-10-17T13:53:21Z

@chrisella - Thanks I downloaded the same version. When you say restart do you mean a Windows restart or Docker for Windows restart ?

crutchfield · 2016-10-17T13:55:24Z

I just downloaded and installed beta and the issue is resolved.

docker version
Client:
Version: 1.12.2
API version: 1.24
Go version: go1.6.3
Git commit: bb80604
Built: Tue Oct 11 05:27:08 2016
OS/Arch: windows/amd64
Experimental: true

Server:
Version: 1.12.2
API version: 1.24
Go version: go1.6.3
Git commit: bb80604
Built: Tue Oct 11 05:27:08 2016
OS/Arch: linux/amd64
Experimental: true

chrisella · 2016-10-17T14:10:48Z

@srinathanand I restarted windows ... which obviously also restarts Docker :) though I didn't do that directly.
I hope you have some luck, since installing that Beta I've gone all day so far and not had any issues

srinathanand · 2016-10-17T14:24:04Z

@chrisella - Restarted both docker and windows with no luck so far. It takes a lot of time trying to start up but fails with the same message every time.

@friism - Do you know what else I can try to fix this problem ? I am on the latest beta (1.12.2-beta28(7813)).

My latest crash report id is -
24C0616A-C2A9-476B-8F52-DF26B11C72F5/2016-10-17_10-00-29

srinathanand · 2016-10-17T14:37:40Z

Here is my Windows version information -

OS Name Microsoft Windows 10 Enterprise
Version 10.0.14393 Build 14393

srinathanand · 2016-10-17T15:32:34Z

UPDATE: Looking back at @cgatian comments I tried to find out if Virtualization was enabled or not for my CPU. I am running a Intel Xeon CPU E5645 @ 2.40 GHz. I downloaded a program called SecurAble and found out that Hardware Virtualization is a No for my CPU and I don't see a Virtualization label when I run Task Manager as shown in the screenshot by cgatian.

I am assuming this is the cause for my Docker for Windows not running. Can someone confirm ?

friism · 2016-10-17T16:46:14Z

@srinathanand yeah, it wouldn't work without that

srinathanand · 2016-10-17T17:02:30Z

Thanks @friism for confirming. Should this be added as a pre-requisite for the Docker for Windows installation ? Just checking the Task Manager should help people if they should use Docker for Windows or the Docker Toolbox.

Current "Getting Started" says this -

Docker for Windows requires 64bit Windows 10 Pro, Enterprise and Education (1511 November update, Build 10586 or later) and Microsoft Hyper-V. Please see What to know before you install for a full list of prerequisites.

friism · 2016-10-17T19:16:39Z

@srinathanand I don't think VirtualBox will work without this either, but adding it to the prerequisites is a good idea.

@londoncalling this is where to find it

guilhermecgs · 2016-11-10T13:10:01Z

same problem with me..

one question: "version/beta28" label means that this bug is already fixed in beta28?

guilhermecgs · 2016-11-10T16:55:35Z

Virtual Box can't do nested virtualization..

So it is not possible to run Windows 10 Pro as guest OS and try to install docker for windows on top of it

rn · 2016-11-30T14:07:17Z

This issue is getting quite messy: some users reported this as fixed, others use a CPU where it won't fix etc. So I'm closing this issue. Should you still have an issue, please open a new issue with details such as diagnostics ID using a recent Beta release
Thanks

devops2017 · 2017-02-03T21:04:39Z

Task Manager showing virtualization is disabled under performance tab. How I can enable it?

I found the way how to enter into BIOS system of Windows 10 OS and enabled it. Now I can see virtualization enabled under task manager and docker is running perfectly.

lisaiceland · 2017-02-16T16:12:32Z

This problem is NOT fixed. Plz don't close this and move on. Needs fixing please. Thnx

rn · 2017-02-16T16:15:00Z

@lisaiceland please read my reason for closing it and suggestion on what to do if you still have the issue here

lisaiceland · 2017-02-16T16:19:25Z

really? we should expect better from a stable release of Docker. Pleas, we can do better really.

lisaiceland · 2017-02-16T16:20:11Z

works fine on MacOS latest for 02/16/2017

srinathanand · 2017-02-16T16:20:43Z

@lisaiceland - have you made sure that Virtualization is enabled?

rn · 2017-02-16T16:28:43Z

@lisaiceland please open a new issue with a diagnostics ID so that we can take a look. This issue is way to messy with lots of different issues posted by users. It's not easy to triage such an issue with so much noise.

In almost all of the case where something like this happens it is actually not an issue with Docker for Windows but most likely an issue with a given Windows installation or interference with other software installed such as security software etc etc.

lisaiceland · 2017-02-16T18:02:58Z

yes. all the recommendations...I have them enabled. Done. Thank You. Lis Regards, Happy Analyzing, Developing, Managing & Launching Dreams Daily! Bless. Ciao! Lisa Kristinardottir (Lis) | Lisaiceland.com | USAGains.com P *Save a tree! Please consider your environmental responsibility before printing. * *Don't print this e-mail unless it's really necessary.* *CONFIDENTIALITY NOTICE* This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank You.

…

On Thu, Feb 16, 2017 at 10:28 AM, Rolf Neugebauer ***@***.***> wrote: @lisaiceland <https://github.com/lisaiceland> please open a new issue with a *diagnostics ID* so that we can take a look. This issue is way to messy with lots of different issues posted by users. It's not easy to triage such an issue with so much noise. In almost all of the case where something like this happens it is actually *not* an issue with Docker for Windows but most likely an issue with a given Windows installation or interference with other software installed such as security software etc etc. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#74 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADbJVizxevpkJZAxqNQpztdGt-oBsFxiks5rdHk_gaJpZM4J5oEC> .

docker-robott · 2020-06-18T03:10:43Z

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

dgageot added kind/bug version/1.12.0 labels Sep 16, 2016

londoncalling mentioned this issue Oct 18, 2016

added beta 29 relnotes placeholders, info for issues re: virtualizati… docker/docs#245

Merged

dgageot added version/beta28 area/hyper-v and removed version/1.12.0 labels Oct 18, 2016

rogaha added the status/triage label Oct 19, 2016

rn closed this as completed Nov 30, 2016

docker locked and limited conversation to collaborators Feb 16, 2017

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

Unable to run Docker for Windows on Windows 10 Ent #74

Unable to run Docker for Windows on Windows 10 Ent #74

Comments

nijel91 commented Sep 10, 2016

Expected behavior

Actual behavior

Information

Steps to reproduce the behavior

dgageot commented Sep 16, 2016

danbeaulieu commented Sep 16, 2016

Gmanweb commented Sep 25, 2016

AndyBerman commented Sep 26, 2016

cgatian commented Sep 28, 2016

cgatian commented Sep 28, 2016

AndyBerman commented Sep 28, 2016

friism commented Sep 29, 2016

chrisella commented Sep 29, 2016 • edited Loading

dev2see commented Sep 30, 2016

crutchfield commented Oct 4, 2016

friism commented Oct 4, 2016

chrisella commented Oct 4, 2016

danbeaulieu commented Oct 4, 2016

husainaloos commented Oct 4, 2016 • edited Loading

danbeaulieu commented Oct 13, 2016

srinathanand commented Oct 14, 2016

AndyBerman commented Oct 14, 2016

srinathanand commented Oct 14, 2016

srinathanand commented Oct 14, 2016

chrisella commented Oct 17, 2016 • edited Loading

srinathanand commented Oct 17, 2016

chrisella commented Oct 17, 2016 • edited Loading

srinathanand commented Oct 17, 2016

crutchfield commented Oct 17, 2016

chrisella commented Oct 17, 2016

srinathanand commented Oct 17, 2016

srinathanand commented Oct 17, 2016

srinathanand commented Oct 17, 2016

friism commented Oct 17, 2016

srinathanand commented Oct 17, 2016

friism commented Oct 17, 2016

guilhermecgs commented Nov 10, 2016 • edited Loading

guilhermecgs commented Nov 10, 2016

rn commented Nov 30, 2016

devops2017 commented Feb 3, 2017 • edited Loading

lisaiceland commented Feb 16, 2017 • edited Loading

rn commented Feb 16, 2017

lisaiceland commented Feb 16, 2017

lisaiceland commented Feb 16, 2017

srinathanand commented Feb 16, 2017

rn commented Feb 16, 2017

lisaiceland commented Feb 16, 2017 via email

docker-robott commented Jun 18, 2020

chrisella commented Sep 29, 2016 •

edited

Loading

husainaloos commented Oct 4, 2016 •

edited

Loading

chrisella commented Oct 17, 2016 •

edited

Loading

chrisella commented Oct 17, 2016 •

edited

Loading

guilhermecgs commented Nov 10, 2016 •

edited

Loading

devops2017 commented Feb 3, 2017 •

edited

Loading

lisaiceland commented Feb 16, 2017 •

edited

Loading