Docker engine stopped windows 10 - Windowsa.top - ваш верный помощник с OS Windows

Docker Engine Stopped on Windows 10

Docker Engine is a popular tool for creating and managing containers. Containers are a lightweight way to package and deploy applications, and they can be used to run applications on a variety of platforms. However, Docker Engine can sometimes stop working on Windows 10. This can be a frustrating problem, but there are a few things you can do to troubleshoot the issue.

In this article, we will discuss the common causes of Docker Engine stopping on Windows 10 and provide some tips on how to fix the problem. We will also cover some best practices for using Docker Engine on Windows 10.

By the end of this article, you will have a better understanding of how Docker Engine works and how to troubleshoot problems when it stops working.

Problem	Solution
Docker engine stopped unexpectedly	Check the Windows Event Viewer for any errors related to Docker. Make sure that the Docker service is running. Reinstall Docker.
Docker engine is not starting	Make sure that the Docker service is enabled. Check the Windows Firewall settings to make sure that Docker is allowed to communicate. Reinstall Docker.
Docker engine is running but containers are not starting	Check the Docker logs for any errors. Make sure that the Docker daemon is running. Make sure that the Docker engine has access to the correct storage location.

Symptoms of a Stopped Docker Engine on Windows 10

If the Docker Engine on your Windows 10 machine is stopped, you may experience the following symptoms:

You cannot run Docker containers.
You cannot create new Docker images.
You cannot push or pull Docker images from a registry.
You may see errors in the Docker logs.
The Docker daemon may not be running.

There are a number of possible causes for a stopped Docker Engine on Windows 10. These include:

A problem with the Docker installation. If the Docker installation is corrupt or incomplete, it may not be able to start properly.
A problem with the Docker daemon. The Docker daemon is the process that runs the Docker Engine. If the daemon is not running, the Docker Engine will not be able to start.
A problem with the Docker configuration. The Docker configuration file, `daemon.json`, contains a number of settings that control the behavior of the Docker Engine. If the configuration file is incorrect or corrupt, the Docker Engine may not be able to start.
A problem with the Docker host. The Docker host is the machine on which the Docker Engine is running. If the host is not properly configured or has problems, the Docker Engine may not be able to start.

How to troubleshoot a stopped Docker Engine on Windows 10

If you are experiencing problems with a stopped Docker Engine on Windows 10, here are a few things you can try to troubleshoot the issue:

1. Check the Docker installation. Make sure that the Docker installation is up-to-date and that all of the required dependencies are installed. You can check the Docker version by running the following command:

docker version

If the Docker version is not up-to-date, you can update it by running the following command:

docker pull docker:latest

2. Check the Docker daemon. Make sure that the Docker daemon is running. You can check the status of the Docker daemon by running the following command:

docker info

If the Docker daemon is not running, you can start it by running the following command:

docker daemon start

3. Check the Docker configuration. Make sure that the Docker configuration file, `daemon.json`, is correct. You can view the contents of the Docker configuration file by running the following command:

cat /etc/docker/daemon.json

If the Docker configuration file is incorrect or corrupt, you can delete it and create a new one. You can find a sample Docker configuration file here:

4. Check the Docker host. Make sure that the Docker host is properly configured and that it has enough resources to run Docker. You can check the Docker host configuration by running the following command:

systemctl status docker

If the Docker host is not properly configured, you can consult the Docker documentation for more information.

5. Reinstall Docker. If you have tried all of the above steps and you are still having problems, you can try reinstalling Docker. You can find instructions on how to reinstall Docker here:

If you are experiencing problems with a stopped Docker Engine on Windows 10, you can use the steps in this guide to troubleshoot the issue. By following these steps, you can usually get the Docker Engine up and running again in no time.

Additional resources

[Docker documentation](https://docs.docker.com/)
[Docker community forums](https://forums.docker.com/)
[Docker support](https://support.docker.com/)

How to troubleshoot a stopped Docker Engine on Windows 10

If your Docker Engine on Windows 10 has stopped working, there are a few things you can do to troubleshoot the issue.

**1. Check the Docker service status**

The first thing you should do is check the status of the Docker service. To do this, open the **Services** app by typing `services` in the Windows search bar. Then, scroll down and find the **Docker Engine** service. If the service is not running, you can start it by clicking the **Start** button.

**2. Check the Docker logs**

If the Docker service is running, but your Docker Engine is still not working, you can check the Docker logs for errors. To do this, open the **Command Prompt** by typing `cmd` in the Windows search bar. Then, type the following command:

docker logs -f

This will display the latest Docker logs. If there are any errors, they will be listed here.

**3. Check your Docker configuration**

If you have recently made any changes to your Docker configuration, it is possible that these changes have caused the Docker Engine to stop working. To check your Docker configuration, open the **Settings** app by typing `settings` in the Windows search bar. Then, click **Apps** > **Manage optional features**. Under the **Docker Engine** section, click **Modify**. This will open the Docker Engine settings. Make sure that all of the settings are correct.

**4. Reinstall Docker Engine**

If you have tried all of the above steps and your Docker Engine is still not working, you may need to reinstall Docker Engine. To do this, open the **Settings** app by typing `settings` in the Windows search bar. Then, click **Apps** > Apps & features. Under the Installed apps section, find the Docker Engine app and click Uninstall. Once Docker Engine has been uninstalled, you can reinstall it from the [Docker website](https://www.docker.com/).

5. Contact Docker support

If you have tried all of the above steps and your Docker Engine is still not working, you can contact Docker support for help. To do this, visit the [Docker support website](https://www.docker.com/support/) and create a support ticket.

How to fix a stopped Docker Engine on Windows 10

If your Docker Engine on Windows 10 has stopped working, there are a few things you can do to fix the issue.

**1. Restart the Docker service**

The first thing you should try is restarting the Docker service. To do this, open the **Services** app by typing `services` in the Windows search bar. Then, scroll down and find the **Docker Engine** service. Right-click the service and select **Restart**.

**2. Check the Docker logs**

docker logs -f

This will display the latest Docker logs. If there are any errors, they will be listed here.

**3. Check your Docker configuration**

**4. Reinstall Docker Engine**

5. Contact Docker support

Q: Why has Docker Engine stopped on my Windows 10 machine?

A: There are a number of reasons why Docker Engine might stop on your Windows 10 machine. Some of the most common reasons include:

Outdated Docker Engine: If you are using an outdated version of Docker Engine, it may not be compatible with the latest updates to Windows 10. To check your Docker Engine version, run the following command in a PowerShell terminal:

docker version

If your version is not up to date, you can update it by following the instructions on the [Docker Engine documentation](https://docs.docker.com/engine/install/).

Insufficient disk space: Docker Engine requires a certain amount of disk space to function properly. If your hard drive is full, Docker Engine may stop working. To check your disk space, run the following command in a PowerShell terminal:

dir c:\

If your disk space is low, you can free up some space by deleting unnecessary files or by moving files to another drive.

Corrupted Docker Engine installation: If your Docker Engine installation is corrupted, it may stop working. To check if your installation is corrupted, run the following command in a PowerShell terminal:

docker info

If you see any errors, you may need to reinstall Docker Engine.

Docker Engine service is not running: The Docker Engine service must be running in order for Docker Engine to function properly. To check if the service is running, run the following command in a PowerShell terminal:

sc query docker

If the service is not running, you can start it by running the following command:

sc start docker

Q: How do I fix Docker Engine not starting on Windows 10?

A: If Docker Engine has stopped on your Windows 10 machine, you can try the following solutions:

Update Docker Engine: If you are using an outdated version of Docker Engine, updating it may fix the problem. To update Docker Engine, follow the instructions on the [Docker Engine documentation](https://docs.docker.com/engine/install/).
Free up disk space: If your hard drive is full, Docker Engine may not have enough space to function properly. To free up some space, delete unnecessary files or move files to another drive.
Reinstall Docker Engine: If your Docker Engine installation is corrupted, reinstalling it may fix the problem. To reinstall Docker Engine, follow the instructions on the [Docker Engine documentation](https://docs.docker.com/engine/install/).
Start the Docker Engine service: If the Docker Engine service is not running, starting it may fix the problem. To start the service, run the following command in a PowerShell terminal:

sc start docker

Q: What are the common problems with Docker Engine on Windows 10?

A: The following are some of the most common problems with Docker Engine on Windows 10:

Docker Engine not starting: This is the most common problem with Docker Engine on Windows 10. The problem can be caused by a number of factors, including an outdated version of Docker Engine, insufficient disk space, or a corrupted Docker Engine installation.
Docker Engine not working with Windows Defender: Windows Defender can sometimes interfere with Docker Engine, causing it to stop working. To fix this problem, you can disable Windows Defender or add Docker Engine to the list of exceptions.
Docker Engine not working with Hyper-V: Hyper-V can sometimes interfere with Docker Engine, causing it to stop working. To fix this problem, you can disable Hyper-V or install Docker Engine on a different machine.

Q: How can I avoid problems with Docker Engine on Windows 10?

A: To avoid problems with Docker Engine on Windows 10, you can follow these tips:

Keep your Docker Engine up to date: Make sure to update Docker Engine to the latest version as soon as possible.
Make sure you have enough disk space: Docker Engine requires a certain amount of disk space to function properly. Make sure you have at least 20GB of free disk space available.
Install Docker Engine on a clean machine: If you are having problems with Docker Engine, try reinstalling it on a clean machine. This will help to ensure that there are no conflicts with other software.
Disable Windows Defender or add Docker Engine to the list of exceptions: If you are using Windows Defender, you may need to disable it or add Docker Engine to the list of exceptions. This will help to prevent Windows Defender from interfering with Docker Engine.

* **

In this blog post, we discussed how to troubleshoot Docker Engine on Windows 10 if it has stopped working. We covered a variety of potential causes for this issue, including corrupted files, missing dependencies, and incorrect permissions. We also provided step-by-step instructions on how to fix each of these problems.

We hope that this blog post has been helpful in resolving your Docker Engine issue. If you have any other questions or concerns, please feel free to reach out to us in the comments section below.

Author Profile

Hatch, established in 2011 by Marcus Greenwood, has evolved significantly over the years. Marcus, a seasoned developer, brought a rich background in developing both B2B and consumer software for a diverse range of organizations, including hedge funds and web agencies.

Originally, Hatch was designed to seamlessly merge content management with social networking. We observed that social functionalities were often an afterthought in CMS-driven websites and set out to change that. Hatch was built to be inherently social, ensuring a fully integrated experience for users.

Now, Hatch embarks on a new chapter. While our past was rooted in bridging technical gaps and fostering open-source collaboration, our present and future are focused on unraveling mysteries and answering a myriad of questions. We have expanded our horizons to cover an extensive array of topics and inquiries, delving into the unknown and the unexplored.

Latest entries

Источник

If you are using Docker Desktop on Windows 10, you might encounter an error message that says “Docker Desktop stopped”. This can be frustrating and prevent you from running your containers and applications. In this tutorial, I will explain what causes this error and how to solve it in four easy steps.

Step 1: Enable Virtualization in BIOS and Install WSL2 Linux Kernel Update

One of the common causes of the Docker Desktop Stopped error on Windows 10 is that your system does not have the required features to run Docker Desktop. These features are virtualization and WSL2. In this step, I will show you how to enable virtualization in BIOS and install WSL2 Linux kernel update on your computer.

Virtualization is a technology that allows your computer to run multiple operating systems or applications in separate environments. This is essential for Docker Desktop because it uses a virtual machine to host the Docker engine and run your containers. To enable virtualization in BIOS, you need to access the BIOS setup menu when you boot your computer. The exact steps may vary depending on your computer model and manufacturer, but usually you need to press a key like F2, F10, or Delete during the boot process. Once you are in the BIOS menu, look for an option called “Virtualization Technology”, “VT-x”, “AMD-V”, or something similar and enable it. Save the changes and exit the BIOS menu.

WSL2 stands for Windows Subsystem for Linux version 2. It is a compatibility layer that allows you to run Linux binaries natively on Windows 10. This is important for Docker Desktop because it uses WSL2 as the backend engine to run Linux containers on Windows. To install WSL2 Linux kernel update, you need to download it from this link: https://wslstorestorage.blob.core.windows.net/wslblob/wsl_update_x64.msi. Run the installer and follow the instructions. You may need to restart your computer again after the installation.

By enabling virtualization in BIOS and installing WSL2 Linux kernel update, you have fixed one of the possible reasons for the Docker Desktop Stopped error on Windows 10. In the next step, I will show you how to check your Docker settings.json file and set wslEngineEnabled to true.

Step 2: Check Your Docker Settings.json File and Set wslEngineEnabled to True

Another potential cause of the Docker Desktop Stopped error on Windows 10 is that your Docker settings.json file does not have the correct configuration for using WSL2 as the backend engine. The settings.json file is located at C:\Users\<username>\AppData\Roaming\Docker\ and contains various options for customizing your Docker experience.

To check your Docker settings.json file and set wslEngineEnabled to true, you need to open the file with a text editor like Notepad or Visual Studio Code. Look for a line that says "wslEngineEnabled": false and change it to "wslEngineEnabled": true. Save the file and close the editor.

By checking your Docker settings.json file and setting wslEngineEnabled to true, you have fixed another possible reason for the Docker Desktop Stopped error on Windows 10. In the next step, I will show you how to uninstall Docker Desktop 4.5.0 and install 4.4.4 instead.

Step 3: Try Uninstalling Docker Desktop 4.5.0 and Installing 4.4.4 Instead

Some users have reported that the Docker Desktop Stopped error on Windows 10 occurs only with Docker Desktop version 4.5.0 and that downgrading to version 4.4.4 solves the problem. This may be due to some bugs or compatibility issues with the latest version of Docker Desktop.

To uninstall Docker Desktop 4.5.0 and install 4.4.4 instead, you need to go to the Control Panel and select “Programs and Features”. Find Docker Desktop in the list of installed programs and click on “Uninstall”. Follow the prompts to remove Docker Desktop from your computer.

Then, download Docker Desktop version 4.4.4 from this link: https://desktop.docker.com/win/stable/amd64/69386/Docker%20Desktop%20Installer.exe. Run the installer and follow the instructions to install Docker Desktop on your computer.

By uninstalling Docker Desktop 4.5.0 and installing 4.4.4 instead, you have fixed another possible reason for the Docker Desktop Stopped error on Windows 10. In the next step, I will show you how to open Hyper-V Manager and connect to your local computer.

Step 4: Open Hyper-V Manager and Connect to Local Computer

The final potential cause of the Docker Desktop Stopped error on Windows 10 is that your Hyper-V Manager is not connected to your local computer. Hyper-V Manager is a tool that allows you to manage virtual machines and networks on your computer or remote servers. Docker Desktop uses Hyper-V Manager to create and run a virtual machine that hosts the Docker engine.

To open Hyper-V Manager and connect to the local computer, you need to press the Windows start button and type “hyper-v”. It will show you Hyper-V Manager in the search results. Open it and select “Connect to Server” from the right panel. A pop-up window will appear where you need to select “Local Computer” and click on “OK”.

By opening Hyper-V Manager and connecting to a local computer, you have fixed the final possible reason for the Docker Desktop Stopped error on Windows 10. You can now try running Docker Desktop again and see if it works without any issues.

You have now completed all the steps to fix the Docker Desktop Stopped error on Windows 10. I hope this tutorial was helpful for you. You have learned how to enable virtualization in BIOS, install WSL2 Linux kernel update package, check your Docker settings.json file, uninstall and install different versions of Docker Desktop, and open Hyper-V Manager and connect to local computer. If you have any questions or feedback, please let me know in the comments below.

Final words

I hope the above-mentioned suggestions will help you resolve the Docker Desktop Stopped error on Windows 10. This error can be annoying and prevent you from using Docker Desktop to run your containers and applications. By following the steps in this tutorial, you should be able to fix the error and enjoy Docker Desktop without any issues.

If you want to learn more about Docker and how to use it for various purposes, I recommend you to visit the “Docker tutorials for beginners” page. There you will find a series of tutorials that will teach you the basics of Docker, such as how to install Docker, how to create and run containers, how to build and share images, how to use Docker Compose and more. These tutorials are designed for beginners who want to get started with Docker and learn by doing.

Thank you for reading this tutorial. I hope you found it useful and informative. If you have any questions or feedback, please let me know in the comments below.

Источник

Description

The dashboard shows that «Docker Engine stopped» after starting docker desktop, cannot load anything related to containers.

Reproduce

From Start Menu click Docker Desktop to start.

Expected behavior

The dashboard of Docker Desktop will show the contents of containers, images, etc..

docker version

Client:
 Version:           27.1.1
 API version:       1.46
 Go version:        go1.21.12
 Git commit:        6312585
 Built:             Tue Jul 23 19:57:57 2024
 OS/Arch:           windows/amd64
 Context:           desktop-linux
error during connect: Get "http://%2F%2F.%2Fpipe%2FdockerDesktopLinuxEngine/v1.46/version": open //./pipe/dockerDesktopLinuxEngine: The system cannot find the file specified.

docker info

Client:
 Version:    27.1.1
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.16.1-desktop.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.1-desktop.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-compose.exe
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.34
    Path:     C:\Program Files\Docker\cli-plugins\docker-debug.exe
  desktop: Docker Desktop commands (Alpha) (Docker Inc.)
    Version:  v0.0.14
    Path:     C:\Program Files\Docker\cli-plugins\docker-desktop.exe
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-dev.exe
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.25
    Path:     C:\Program Files\Docker\cli-plugins\docker-extension.exe
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     C:\Program Files\Docker\cli-plugins\docker-feedback.exe
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.3.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-init.exe
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-sbom.exe
  scout: Docker Scout (Docker Inc.)
    Version:  v1.11.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-scout.exe

Server:
ERROR: error during connect: Get "http://%2F%2F.%2Fpipe%2FdockerDesktopLinuxEngine/v1.46/info": open //./pipe/dockerDesktopLinuxEngine: The system cannot find the file specified.
errors pretty printing info

Diagnostics ID

3AF8C900-1E3C-4A57-82FB-2AB4FC6C8BF3/20240819004144

Additional Info

Related logs

Logs from dockerd.log (in %LocalAppData%\Docker\log\vm\dockerd.log)

-------------------------------------------------------------------------------->8
time="2024-08-19T00:31:34.365459802Z" level=info msg="Starting up"
time="2024-08-19T00:31:34.444348218Z" level=info msg="Starting daemon with containerd snapshotter integration enabled"
time="2024-08-19T00:31:34.444434560Z" level=info msg="Loading containers: start."
time="2024-08-19T00:31:35.357257668Z" level=info msg="Removing stale sandbox 316633c7275375d42a5c6fea152f74ba70bf812f1cc133107b4e08147ce4f789 (12e64acb4c34b04b708dc97c91907ac9fe17940415f222b32cddcc3c5816aaa3)"
time="2024-08-19T00:31:35.388736011Z" level=warning msg="Error (Unable to complete atomic operation, key modified) deleting object [endpoint 9fab5c953d8b7b66b80f58c1f04ee78e8cb98afad7ba95e0a45030bc0143d7af 8d3b767dcddd6297e2221c2f6698ccae080a792f7267118ad16809f9acb356b5], retrying...."
time="2024-08-19T00:31:35.403423963Z" level=info msg="Removing stale sandbox 3c98d4cf52f9141f255264638968437c4bb9eb59d040facd687e3b808a2673f3 (bef615aff10891bb14e8b77bdbb620daba4fc4f4345439b328f35afa05c4dfe2)"
time="2024-08-19T00:31:35.416411983Z" level=warning msg="Error (Unable to complete atomic operation, key modified) deleting object [endpoint f612762be574826fc573337c8e11ebc004f758f90092771980a4dadb8efc807a 8a3090b10442016053223927c1ddf7f6e61600d2961632c7b2b17b44deb6c179], retrying...."
time="2024-08-19T00:31:35.431102469Z" level=info msg="Removing stale sandbox a05715201481324883adf7db938edea8e7ff859974710ea46f2828396f564b78 (986edbb47c140e21af00f3bc689afb8dc6f1579aab20e984f179994e51f3da98)"
time="2024-08-19T00:31:35.462801221Z" level=warning msg="Error (Unable to complete atomic operation, key modified) deleting object [endpoint 9fab5c953d8b7b66b80f58c1f04ee78e8cb98afad7ba95e0a45030bc0143d7af e5fd129f9b376ba3260f7d60e5ba4e285abac15ab7aa87515d600eadffa7ad08], retrying...."
time="2024-08-19T00:31:35.476894200Z" level=info msg="Removing stale sandbox ed22162bc6959b8622f35d3abe0ff10840ce689f3c20d4be72754a07ffcc2a89 (be96da85178bd20db9b10bd78f68244588194eb87e64c69fc8771980bd7f8b5a)"
time="2024-08-19T00:31:35.499638567Z" level=warning msg="Error (Unable to complete atomic operation, key modified) deleting object [endpoint e747fdd1dbfb15953a74d62ed0ea3a2aa2025dad382ed197b93df30739abc97b 240d58c594dac3d373da5214a9ef63de187384ff7ac7ebace37c760536a42804], retrying...."
time="2024-08-19T00:31:35.513964661Z" level=info msg="Removing stale sandbox 379e69a6c8b3c10f5cf8775091174459c13d34f45f7d16930446a7f4204f8d49 (6ce5ae0c94b8a9b34ed322cd598387dd1e244389028b8414862bb39d8fa593f4)"
time="2024-08-19T00:31:35.524382315Z" level=warning msg="Failed to clean up network resources on container coder-coder-traefik-1 disconnect: failed to set gateway while updating gateway: route for the gateway 192.168.200.1 could not be found: network is unreachable"
time="2024-08-19T00:31:35.537070624Z" level=warning msg="Error (Unable to complete atomic operation, key modified) deleting object [endpoint 4306cace9fe375314ecdacbb84c1bac1321a67739767f2757d7068f88f4dce19 e2973ca19da1dc950ea58d9708e5385aa015e881ce4135790f73b74ae1cee2f7], retrying...."
time="2024-08-19T00:31:35.559286083Z" level=warning msg="Error (Unable to complete atomic operation, key modified) deleting object [endpoint 9fab5c953d8b7b66b80f58c1f04ee78e8cb98afad7ba95e0a45030bc0143d7af 186d3e8f5f2dfa0f6166acdbfa1d406c309ef13b1eb4c540cbdad805a6f80113], retrying...."
(......similial logs omitted......)
time="2024-08-19T00:31:36.214947358Z" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
time="2024-08-19T00:31:36.300543470Z" level=warning msg="error locating sandbox id ed65de9b78106adf2c221e7ac5799350505db1723ef8e0ea5121895d17861ca8: sandbox ed65de9b78106adf2c221e7ac5799350505db1723ef8e0ea5121895d17861ca8 not found"
(......similial logs omitted......)
time="2024-08-19T00:31:40.522861957Z" level=info msg="Loading containers: done."
time="2024-08-19T00:31:40.537903978Z" level=warning msg="WARNING: daemon is not using the default seccomp profile"
time="2024-08-19T00:31:40.537982450Z" level=info msg="Docker daemon" commit=cc13f95 containerd-snapshotter=true storage-driver=overlayfs version=27.1.1
time="2024-08-19T00:31:40.538088271Z" level=info msg="Daemon has completed initialization"
context deadline exceeded
time="2024-08-19T00:31:55.623122430Z" level=info msg="stopping event stream following graceful shutdown" error="context canceled" module=libcontainerd namespace=plugins.moby
time="2024-08-19T00:31:55.623218359Z" level=info msg="stopping event stream following graceful shutdown" error="context canceled" module=libcontainerd namespace=moby
EOF

A long time after Docker Desktop showing that Docker Engine Stopped, the trobleshooting dialogue will prompt with the follow message entitled with An unexpected error occurred:

running engine: waiting for the Docker API: context deadline exceeded

update

I have been switching to the containerd storage backend for several versions of docker desktop. Now, I tries to switch back to the default storage engine. Surprisingly, docker engine can be started normally. So, If this problem close related to the storage engine, though I have not found any obvious clue from the containerd logs.

The issue is probably related to containerd failure, see the related logs.
Related logs of containerd (C:\Users\gary\AppData\Local\Docker\log\vm\containerd.log)

time="2024-08-30T00:58:39.719359178Z" level=info msg="shim disconnected" id=cd862bef32f3a78a06ac7f6cb6ec45d0c9d238727ef01cb8a48a6c86553c4945 namespace=moby
time="2024-08-30T00:58:39.719832054Z" level=warning msg="cleaning up after shim disconnected" id=cd862bef32f3a78a06ac7f6cb6ec45d0c9d238727ef01cb8a48a6c86553c4945 namespace=moby
time="2024-08-30T00:58:39.719848855Z" level=info msg="cleaning up dead shim" namespace=moby
time="2024-08-30T00:58:39.720904191Z" level=info msg="shim disconnected" id=d5451d1f386d450990a72d8478119307918b8bf050a52eca6e371ed2e74d47a1 namespace=moby
time="2024-08-30T00:58:39.720967939Z" level=warning msg="cleaning up after shim disconnected" id=d5451d1f386d450990a72d8478119307918b8bf050a52eca6e371ed2e74d47a1 namespace=moby
time="2024-08-30T00:58:39.720980026Z" level=info msg="cleaning up dead shim" namespace=moby
time="2024-08-30T00:58:39.734869728Z" level=warning msg="cleanup warnings time=\"2024-08-30T00:58:39Z\" level=warning msg=\"failed to read init pid file\" error=\"open /var/run/desktop-containerd/daemon/io.containerd.runtime.v2.task/moby/cd862bef32f3a78a06ac7f6cb6ec45d0c9d238727ef01cb8a48a6c86553c4945/init.pid: no such file or directory\" runtime=io.containerd.runc.v2\n" namespace=moby
time="2024-08-30T00:58:39.736270991Z" level=error msg="copy shim log" error="read /proc/self/fd/48: file already closed" namespace=moby
time="2024-08-30T00:58:39.739085555Z" level=warning msg="cleanup warnings time=\"2024-08-30T00:58:39Z\" level=warning msg=\"failed to read init pid file\" error=\"open /var/run/desktop-containerd/daemon/io.containerd.runtime.v2.task/moby/d5451d1f386d450990a72d8478119307918b8bf050a52eca6e371ed2e74d47a1/init.pid: no such file or directory\" runtime=io.containerd.runc.v2\n" namespace=moby
time="2024-08-30T00:58:39.740396488Z" level=error msg="copy shim log" error="read /proc/self/fd/46: file already closed" namespace=moby

The folders under \\wsl.localhost\docker-desktop-data\data\desktop-containerd\daemon\io.containerd.runtime.v2.task\moby are actually all empty. Hence, there is no init.pid.

companion logs from dockerd.log:

time="2024-08-30T01:12:00.716139441Z" level=debug msg="2024/08/30 01:12:00 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: \"/run/containerd/containerd.sock\", ServerName: \"localhost\", Attributes: {\"<%!p(networktype.keyType=grpc.internal.transport.networktype)>\": \"unix\" }, }. Err: connection error: desc = \"transport: Error while dialing: dial unix:///run/containerd/containerd.sock: timeout\"" library=grpc
time="2024-08-30T01:12:03.270088474Z" level=debug msg="2024/08/30 01:12:03 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: \"/run/containerd/containerd.sock\", ServerName: \"localhost\", Attributes: {\"<%!p(networktype.keyType=grpc.internal.transport.networktype)>\": \"unix\" }, }. Err: connection error: desc = \"transport: Error while dialing: dial unix:///run/containerd/containerd.sock: timeout\"" library=grpc

Источник

Why is my Docker engine stopped?
Why is Docker not working Windows 10?
What to do if Docker is not running?
How do I stop Docker containers from stopping?
Can docker run on Windows Home?
How do I run Docker daemon on Windows?
Where is my Docker daemon running?
What happens when we restart Docker?
How do I stop Docker daemon in Windows?

Why is my Docker engine stopped?

This happens if you run a foreground container (using docker run ), and then press Ctrl+C when the program is running. When this happens, the program will stop, and the container will exit. The container has been stopped using docker stop : You can manually stop a container using the docker stop command.

Why is Docker not working Windows 10?

Docker Desktop fails to start when anti-virus software is installed. Some anti-virus software may be incompatible with Hyper-V and Microsoft Windows 10 builds. The conflict typically occurs after a Windows update and manifests as an error response from the Docker daemon and a Docker Desktop start failure.

What to do if Docker is not running?

By default, docker container will exit immediately if you do not have any task running on the container. To keep the container running in the background, try to run it with —detach (or -d ) argument.

How do I stop Docker containers from stopping?

According to this answer, adding the -t flag will prevent the container from exiting when running in the background. You can then use docker exec -i -t <image> /bin/bash to get into a shell prompt.

Can docker run on Windows Home?

We are now pleased to announce that we have completed the work to enable experimental support for Windows Home WSL 2 integration. This means that Windows Insider users on 19040 or higher can now install and use Docker Desktop! Feedback on this first version of Docker Desktop for Windows Home is welcomed!

How do I run Docker daemon on Windows?

To start Docker in daemon mode, choose Application > Start «Docker Daemon». The state should transition to «Running» after a few seconds and Docker Daemon should be accessible over the remote bridge. That’s it! Next time your computer boots, Docker Daemon will start up immediately, before anyone logs on.

Where is my Docker daemon running?

Another way to check for a running Docker daemon is by inspecting its process ID file. The daemon writes its process ID to /var/run/docker. pid each time it starts up. When this file exists, Docker should be running and ready for CLI connections.

What happens when we restart Docker?

Docker provides restart policies to control whether your containers start automatically when they exit, or when Docker restarts. Restart policies ensure that linked containers are started in the correct order. Docker recommends that you use restart policies, and avoid using process managers to start containers.

How do I stop Docker daemon in Windows?

To stop Docker when you have started it manually, issue a Ctrl+C in your terminal.

Источник

Было уже.
Ставьте линукс или виртуалку с линуксом и будет вам счастье.

1 Для кросплатформеных систем желательно винда PRO.
2 Вижуал стайшн от микрософта много чего включает в себя.
3 посмотрите как через повершел в винде, линух параллельно поставить. Нужен пароль администратора)))

За долгие годы все попытки использование подобных проектов на винде ни к чему не приводили, только желание изучать пропадало.

Виртуалку ставьте с линухой.

Зачем docker desktop, когда можно докер прям в wsl2 поставить?
Если хочется GUI, то есть portainer

UPD: сейчас переехал на podman + podman Desktop в качестве GUI — полёт вцелом нормальный, настраивается всё легко. В целом совместим со всеми инструментами для докера. Проблема пока только с docker-compose, который не хочет на подмане подниматься.

Напишу, если кто будет искать это решение:
Во первых проверяем, что по умолчанию включен wsl 2, во вторых, что компьютер поддерживает виртуализацию и она включена в биосе, далее в компонентах виндовс включаем Hyper и Контейнеры.
Также, я обратил внимание, что когда мне казалось, что Докер висит, я посмотрел, что в процессах идет нагрузка на WiFI, шло активное скачивание.
Тогда я оставил компьютер на полчаса в таком состоянии и в какой то момент Докер успешно стартанул. Я прихожу к выводу, что после первого запуска Докер для рабочего стола что-то усиленно докачивает в систему, но это не совсем очевидно выглядит. Потому не прерывайте первый запуск, если вам кажется, что все зависло.

Ненадо ставить докер в винду
Виртуалка с линукс и на неё докер…

Попробуйте еще установить Rancher Desktop — переключитесь там на докер. Работает вполне стабильно!

зайди в биос и включи виртуализацию, тогда запуститься

Источник