-
Notifications
You must be signed in to change notification settings - Fork 283
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 Daemon is not running #2671
Comments
same issue with me. |
Run this as Administrator |
I tried that option too. You mean docker/ PowerShell |
Yes, but try also cmd. Like dockerd in powershell and docker in cmd. And stop the service when you start with that. |
Same issue happening to me. Tried different options and doesn't solve it :
|
Ok what says dockerd? When your runn it in powershell (Do you have the nat interface, do you stop the service....)?? |
same issue with me. |
Same here |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an 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. |
I had to go through this problem. The solution was posted in (#1825). |
worked for me! |
@Ankit3794 getting the below error while running the above command
|
Closed issues are locked after 30 days of inactivity. 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. |
Windows 10 Pro
PS C:\WINDOWS\system32> docker --version
Docker version 18.06.1-ce, build e68fc7a
PS C:\WINDOWS\system32> docker ps
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.38/containers/json: 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.
The text was updated successfully, but these errors were encountered: