Useful or not, from you.
for-win Error response from daemon: open \\.\pipe\docker_engine_linux: The system cannot find the file specified

<!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation --> <!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->
  • [x] I have tried with the latest version of my channel (Stable or Edge)
  • [x] I have uploaded Diagnostics
  • Diagnostics ID: C2A98F22-D776-49B5-BF5C-5F2E5D48909F/20200811112537

Expected behaviour

So docker was running normally however after I restarted my computer docker should have started and run normally

Actual behaviour

docker: Error response from daemon: open \\.\pipe\docker_engine_linux: The system cannot find the file specified.

No matter what command I run I get this error

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?

  • Is the problem new?

  • Did the problem appear with an update?

  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->

  • Windows Version: Win10 home 2004

  • Docker Desktop Version:

  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: Virtualized windows locally

  • The completely new problem never happened before

  • I do not know whether it is reproducible

Steps to reproduce the behaviour

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

Nothing just restarted despite not even using docker previously.

That's a useful answer
Without any help

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