New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
nijel91 opened this Issue Sep 10, 2016 · 43 comments

Comments

Projects
None yet
@nijel91

nijel91 commented Sep 10, 2016

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

This comment has been minimized.

Show comment
Hide comment
@dgageot

dgageot Sep 16, 2016

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?

dgageot commented Sep 16, 2016

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

This comment has been minimized.

Show comment
Hide comment
@danbeaulieu

danbeaulieu Sep 16, 2016

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)

danbeaulieu commented Sep 16, 2016

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

This comment has been minimized.

Show comment
Hide comment
@Gmanweb

Gmanweb Sep 25, 2016

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)

Gmanweb commented Sep 25, 2016

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

This comment has been minimized.

Show comment
Hide comment
@AndyBerman

AndyBerman Sep 26, 2016

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

AndyBerman commented Sep 26, 2016

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

@cgatian

This comment has been minimized.

Show comment
Hide comment
@cgatian

cgatian Sep 28, 2016

Any resolution to this?

cgatian commented Sep 28, 2016

Any resolution to this?

@cgatian

This comment has been minimized.

Show comment
Hide comment
@cgatian

cgatian Sep 28, 2016

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.

image

cgatian commented Sep 28, 2016

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.

image

@AndyBerman

This comment has been minimized.

Show comment
Hide comment
@AndyBerman

AndyBerman Sep 28, 2016

It shows Virtualization is Enabled.

AndyBerman commented Sep 28, 2016

It shows Virtualization is Enabled.

@friism

This comment has been minimized.

Show comment
Hide comment
@friism

friism Sep 29, 2016

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

friism commented Sep 29, 2016

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

@chrisella

This comment has been minimized.

Show comment
Hide comment
@chrisella

chrisella Sep 29, 2016

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)

chrisella commented Sep 29, 2016

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

This comment has been minimized.

Show comment
Hide comment
@dev2see

dev2see Sep 30, 2016

The same problem

dev2see commented Sep 30, 2016

The same problem

@crutchfield

This comment has been minimized.

Show comment
Hide comment
@crutchfield

crutchfield Oct 4, 2016

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

crutchfield commented Oct 4, 2016

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

This comment has been minimized.

Show comment
Hide comment
@friism

friism Oct 4, 2016

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

friism commented Oct 4, 2016

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

@chrisella

This comment has been minimized.

Show comment
Hide comment
@chrisella

chrisella Oct 4, 2016

@friism Excellent great news! :)
thanks

chrisella commented Oct 4, 2016

@friism Excellent great news! :)
thanks

@danbeaulieu

This comment has been minimized.

Show comment
Hide comment
@danbeaulieu

danbeaulieu Oct 4, 2016

@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

danbeaulieu commented Oct 4, 2016

@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

This comment has been minimized.

Show comment
Hide comment
@husainaloos

husainaloos Oct 4, 2016

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

husainaloos commented Oct 4, 2016

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

This comment has been minimized.

Show comment
Hide comment
@danbeaulieu

danbeaulieu Oct 13, 2016

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

danbeaulieu commented Oct 13, 2016

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

This comment has been minimized.

Show comment
Hide comment
@srinathanand

srinathanand Oct 14, 2016

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

srinathanand commented Oct 14, 2016

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

This comment has been minimized.

Show comment
Hide comment
@AndyBerman

AndyBerman Oct 14, 2016

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

AndyBerman commented Oct 14, 2016

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

@srinathanand

This comment has been minimized.

Show comment
Hide comment
@srinathanand

srinathanand Oct 14, 2016

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

srinathanand commented Oct 14, 2016

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

@srinathanand

This comment has been minimized.

Show comment
Hide comment
@srinathanand

srinathanand Oct 14, 2016

@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

srinathanand commented Oct 14, 2016

@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

This comment has been minimized.

Show comment
Hide comment
@chrisella

chrisella Oct 17, 2016

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.

chrisella commented Oct 17, 2016

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

This comment has been minimized.

Show comment
Hide comment
@srinathanand

srinathanand Oct 17, 2016

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

srinathanand commented Oct 17, 2016

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

@chrisella

This comment has been minimized.

Show comment
Hide comment
@chrisella

chrisella commented Oct 17, 2016

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

@srinathanand

This comment has been minimized.

Show comment
Hide comment
@srinathanand

srinathanand Oct 17, 2016

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

srinathanand commented Oct 17, 2016

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

@crutchfield

This comment has been minimized.

Show comment
Hide comment
@crutchfield

crutchfield Oct 17, 2016

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

crutchfield commented Oct 17, 2016

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

This comment has been minimized.

Show comment
Hide comment
@chrisella

chrisella Oct 17, 2016

@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

chrisella commented Oct 17, 2016

@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

This comment has been minimized.

Show comment
Hide comment
@srinathanand

srinathanand Oct 17, 2016

@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 commented Oct 17, 2016

@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

This comment has been minimized.

Show comment
Hide comment
@srinathanand

srinathanand Oct 17, 2016

Here is my Windows version information -

OS Name Microsoft Windows 10 Enterprise
Version 10.0.14393 Build 14393

srinathanand commented Oct 17, 2016

Here is my Windows version information -

OS Name Microsoft Windows 10 Enterprise
Version 10.0.14393 Build 14393

@srinathanand

This comment has been minimized.

Show comment
Hide comment
@srinathanand

srinathanand Oct 17, 2016

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 ?

srinathanand commented Oct 17, 2016

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

This comment has been minimized.

Show comment
Hide comment
@friism

friism Oct 17, 2016

@srinathanand yeah, it wouldn't work without that

friism commented Oct 17, 2016

@srinathanand yeah, it wouldn't work without that

@srinathanand

This comment has been minimized.

Show comment
Hide comment
@srinathanand

srinathanand Oct 17, 2016

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.

srinathanand commented Oct 17, 2016

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

This comment has been minimized.

Show comment
Hide comment
@friism

friism Oct 17, 2016

@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

image

friism commented Oct 17, 2016

@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

image

@guilhermecgs

This comment has been minimized.

Show comment
Hide comment
@guilhermecgs

guilhermecgs Nov 10, 2016

same problem with me..

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

guilhermecgs commented Nov 10, 2016

same problem with me..

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

@guilhermecgs

This comment has been minimized.

Show comment
Hide comment
@guilhermecgs

guilhermecgs Nov 10, 2016

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

guilhermecgs commented Nov 10, 2016

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

This comment has been minimized.

Show comment
Hide comment
@rn

rn Nov 30, 2016

Contributor

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

Contributor

rn commented Nov 30, 2016

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

@rn rn closed this Nov 30, 2016

@devops2017

This comment has been minimized.

Show comment
Hide comment
@devops2017

devops2017 Feb 3, 2017

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.

devops2017 commented Feb 3, 2017

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

This comment has been minimized.

Show comment
Hide comment
@lisaiceland

lisaiceland Feb 16, 2017

ice_screenshot_20170216-101536
ice_screenshot_20170216-101551
ice_screenshot_20170216-101615
ice_screenshot_20170216-101653

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

lisaiceland commented Feb 16, 2017

ice_screenshot_20170216-101536
ice_screenshot_20170216-101551
ice_screenshot_20170216-101615
ice_screenshot_20170216-101653

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

@rn

This comment has been minimized.

Show comment
Hide comment
@rn

rn Feb 16, 2017

Contributor

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

Contributor

rn commented Feb 16, 2017

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

@lisaiceland

This comment has been minimized.

Show comment
Hide comment
@lisaiceland

lisaiceland Feb 16, 2017

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

lisaiceland commented Feb 16, 2017

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

@lisaiceland

This comment has been minimized.

Show comment
Hide comment
@lisaiceland

lisaiceland Feb 16, 2017

works fine on MacOS latest for 02/16/2017

lisaiceland commented Feb 16, 2017

works fine on MacOS latest for 02/16/2017

@srinathanand

This comment has been minimized.

Show comment
Hide comment
@srinathanand

srinathanand Feb 16, 2017

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

srinathanand commented Feb 16, 2017

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

@rn

This comment has been minimized.

Show comment
Hide comment
@rn

rn Feb 16, 2017

Contributor

@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.

Contributor

rn commented Feb 16, 2017

@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

This comment has been minimized.

Show comment
Hide comment
@lisaiceland

lisaiceland Feb 16, 2017

lisaiceland commented Feb 16, 2017

@docker docker locked and limited conversation to collaborators Feb 16, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.