docker-robott
commented
4 years ago 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
Expected behavior
Docker to Start
Actual behavior
Docker is failing to start Unable to create: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The Hyper-V Management Tools could not access an expected WMI class on computer 'AL01HYPV12'. This may indicate that the Hyper-V Platform is not installed on the computer or that the version of the Hyper-V Platform is incompatible with these management tools. at New-Switch,: line 117
at , : line 394
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 75
at Docker.Actions.<>cDisplayClass16_0.b0() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 61
at Docker.WPF.TaskQueue.<>cDisplayClass19_0.<.ctor>b 1() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59
Information
Diagnostic ID = 65778450-BE30-4BF2-BA16-30ACDED9B0E3/2018-02-14_12-42-28 OS = Windows Server 2016 v1607 OS Build 14393.2068 Server =ProLiant BL460c Gen8 Docker Version 18.02.0-ce-win52 (15732) Channel: edge 92c7ac6
Steps to reproduce the behavior
1) Install Docker 2) Start Docker 3) observe failure
I am able to restart Docker by right clicking on the icon in the taskbar and it will start, but it doesn't function correctly.
I am running this from an Administrator: Command Prompt
C:>docker run hello-world docker: error during connect: Post http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.36/containers/create: 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. See 'docker run --help'.
C:>docker version Client: Version: 18.02.0-ce API version: 1.36 Go version: go1.9.3 Git commit: fc4de44 Built: Wed Feb 7 21:12:53 2018 OS/Arch: windows/amd64 Experimental: false Orchestrator: swarm error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.36/version: 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.
Notes
With a fresh install of Windows 2016, i was able to isntall the non-beta edition of docker. Then After windows updates installed all the security updates, docker failed to start. I tried downloaded the beta version of docker and it still fails to start. I am able to get deocker to start by by right clicking on the icon in the taskbar and selectign restart, but it doesn't function correctly.
Log
Version: 18.02.0-ce-win52 (15732) Channel: edge Sha1: 92c7ac6fd6d2f3876329f394b1482a0d89211762 Started on: 2018/02/14 14:23:20.649 Resources: C:\Program Files\Docker\Docker\Resources OS: Windows Server 2016 Standard Edition: ServerStandard Id: 1607 Build: 14393 BuildLabName: 14393.2068.amd64fre.rs1_release.180209-1727 File: C:\Users\srv-veritas\AppData\Local\Docker\log.txt CommandLine: "C:\Program Files\Docker\Docker\Docker for Windows.exe" You can send feedback, including this log file, at https://github.com/docker/for-win/issues [14:23:20.790][GUI ][Info ] Starting... [14:23:20.805][GUI ][Error ] An instance is already running. Exiting. [14:23:23.102][NamedPipeClient][Info ] Received response for DownloadWinContainersDebugInfo [14:23:23.102][NamedPipeServer][Info ] DownloadWinContainersDebugInfo done in 00:00:06.7391163. [14:23:25.477][NamedPipeClient][Info ] Received response for GetDebugInfo [14:23:25.477][NamedPipeServer][Info ] GetDebugInfo done in 00:00:09.1122665. [14:23:25.587][CrashReport ][Info ] Uploading diagnostics... [14:23:27.478][CrashReport ][Info ] Diagnostics successfully uploaded (65778450-BE30-4BF2-BA16-30ACDED9B0E3/2018-02-14_14-23-16) [14:23:27.493][GUI ][Info ] Sending Bugsnag report 42aab5c6-7b65-419d-b9c0-6fc9f246e45f... [14:23:28.822][GUI ][Info ] Bugsnag report 42aab5c6-7b65-419d-b9c0-6fc9f246e45f sent [14:37:59.289][SegmentApi ][Info ] Usage statistic: actionMenuFeedback [14:37:59.539][NamedPipeClient][Info ] Sending Version()... [14:37:59.539][NamedPipeClient][Info ] Received response for Version [14:37:59.539][NamedPipeClient][Info ] Sending TryGetVhdxSize()... [14:37:59.539][NamedPipeServer][Info ] Version() [14:37:59.539][NamedPipeServer][Info ] Version done in 00:00:00. [14:37:59.554][NamedPipeServer][Info ] TryGetVhdxSize() [14:37:59.554][PowerShell ][Info ] Run script 'Get-VHD –Path "" | select -ExpandProperty Size'... [14:37:59.585][NamedPipeClient][Info ] Received response for TryGetVhdxSize [14:37:59.585][NamedPipeServer][Info ] TryGetVhdxSize done in 00:00:00.0312441. [14:38:03.920][FeedbackSettings][Info ] Open logs