Skip to content
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

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

Closed
JasmineB1995 opened this issue Mar 12, 2019 · 3 comments
Closed

Comments

@JasmineB1995
Copy link

• Which version of dockers are you using: Community or Enterprise Edition? - Community
• Is this a brand new installation? – No. My user who reported the issue have been using it for some time.
• Name and edition of the product –

• Output from “Docker version” and “Docker info”
• Microsoft Windows [Version 10.0.17134.619]
• (c) 2018 Microsoft Corporation. All rights reserved.

• C:\WINDOWS\system32>docker version
• Client: Docker Engine - Community
• Version: 18.09.2
• API version: 1.39
• Go version: go1.10.8
• Git commit: 6247962
• Built: Sun Feb 10 04:12:31 2019
• OS/Arch: windows/amd64
• Experimental: false
• error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.39/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.

• C:\WINDOWS\system32>
C:\WINDOWS\system32>docker info
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.39/info: 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.
C:\WINDOWS\system32>

• Reproducible steps if available: Just open a command prompt and run docker PS or any other command.
• Full Error message (including docker command)

• When this happened: After upgrading machine from 1703 to 1803.
• Docker installation on machine

@docker-robott
Copy link
Collaborator

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

@LeonardAB
Copy link

Related to #1927

@docker-robott
Copy link
Collaborator

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 docker locked and limited conversation to collaborators Jul 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants