«Docker Desktop stopped. » message after installation [closed]
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago .
The community reviewed whether to reopen this question 1 year ago and left it closed:
Original close reason(s) were not resolved
- uninstalling and reinstalling again
- run application as administrator
asked Feb 11, 2022 at 18:13
795 1 1 gold badge 5 5 silver badges 8 8 bronze badges
For me restarting docker from the taskbar tray fixed the issue.
Apr 15, 2022 at 14:29
In my case it started working after installing: «WSL2 Linux kernel update package for x64 machines». More info here: superuser.com/questions/1584710/…
May 15, 2022 at 18:12
First, I had to update the kernel ( github.com/microsoft/WSL/issues/5650#issuecomment-663845956 ). Then I went to Debug -> Clean / Purge Data -> WSL 2 -> Delete. Then It worked.
Jun 7, 2022 at 18:35
Enable Virtualization for your system.
Sep 26, 2022 at 11:27
In my case, i had to enable virtualization in CPU config tab in vcenter for my win10 virtual machine.
Nov 21, 2022 at 6:47
5 Answers 5
Just go to the config file at C:\Users\\AppData\Roaming\Docker\settings.json , and set «wslEngineEnabled»: true
I had to restart after saving.
answered Feb 13, 2022 at 22:26
Daniel Parrott Daniel Parrott
221 1 1 silver badge 2 2 bronze badges
This solved the problem with my machine. I noticed that when I opened the settings in the app itself when it showed that it stopped, the WSL engine was not checked. That led me here. Nice find. I have an XPS 9500 running Windows 11 Home.
Feb 13, 2022 at 22:39
Thank you for you .I solved this problem.
Feb 14, 2022 at 15:10
Works perfectly for Docker v4.5
Feb 14, 2022 at 21:51
This doesn’t work.
Sep 26, 2022 at 22:09
This setting wslEngineEnabled was set to true but I still faced issues.
Oct 3, 2022 at 18:47
I had the same problem. If you are using docker 4.5.0, try uninstall and install 4.4.4 instead. That worked for me.
answered Feb 11, 2022 at 20:48
117 4 4 bronze badges
additionaly i had to enable virtualization in the bios and update linux kernel
Feb 13, 2022 at 11:20
This doesn’t work.
Sep 26, 2022 at 22:09
This worked for me. I installed 4.6.0 for windows 10 machine.
Nov 26, 2022 at 4:09
A new version of Docker Desktop (4.5.1), released on 2022-02-15 fixes this problem.
If you are running Docker Desktop on Windows Home, installing 4.5.1 will switch it back to WSL 2 automatically. If you are running another version of Windows, and you want Docker Desktop to use the WSL 2 backend, you must manually switch by enabling the Use the WSL 2 based engine option in the Settings > General section. Alternatively, you can edit the Docker Desktop settings file located at %APPDATA%\Docker\settings.json and manually switch the value of the wslEngineEnabled field to true.
Как оживить docker на windows 10?
Подскажите пожалуйста как побороть данную болезнь и запустить докер на windows 10?
У меня windows 10, home версия
Установил с офф сайта docker desctop для windows
Предварительно включил виртуализацию через биос.
Запускаю docker desctop
Он выдает Docker Desktop stopped. при этом кит анимирует в треи бесконечно, если кликнуть в настройки то там лоадер тоже бесконечный.
Если в консоли попытаться вызвать команду докера вываливается ошибка error during connect: This error may indicate that the docker daemon is not running.: Get «http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/version»: open //./pipe/docker_engine: The system cannot find the file specified.
Если попытаться скачать образ удаленный пишет error during connect: This error may indicate that the docker daemon is not running.: Post «http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/images. «: open //./pipe/docker_engine: The system cannot find the file specified.
- Вопрос задан более года назад
- 12809 просмотров
2 комментария
Простой 2 комментария
How to Fix Docker Desktop Stopped Error on Windows 10
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.
Table of Contents
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\\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.
Related Posts:
- Docker for Beginners: An Introduction to Docker,…
- Docker and DevOps: How Docker Integrates with CI/CD…
- How to Tell How Much Memory a Docker Container Uses?
- How to Install Docker on MacOS?
- How to Install Docker on Ubuntu 22.04
- How to Start MySQL in Docker Container
- Docker Compose Tutorial for Beginners
- How to Build Docker Image and Run the Container?
- How to View Docker Container Logs?
- Zero Downtime Deployments with Docker and NGINX
Posted in: Docker
Tagged: Docker
Written by Sergey Kargopolov
I’m a software developer with a passion for teaching. I’ve written lots of articles for AppsDeveloperBlog.com and made plenty of video tutorials on my YouTube channel(https://youtube.com/@SergeyKargopolov). If you want to dive deeper, I’ve also got some courses on Udemy(https://www.udemy.com/user/sergeykargopolov/) you might like.
When I’m not coding, I love to travel. I also share my travel adventures over at TravelLocalCanada.com. Hope to see you around on one of these platforms!
Saved searches
Use saved searches to filter your results more quickly
Cancel Create saved search
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
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 desktop writes «docker engine stopped» #139
VasKonstV opened this issue Apr 10, 2023 · 10 comments
Docker desktop writes «docker engine stopped» #139
VasKonstV opened this issue Apr 10, 2023 · 10 comments
Comments
VasKonstV commented Apr 10, 2023 •
- I have tried with the latest version of Docker Desktop 4.18.0
- The operation system is Ubuntu 22.04.1 LTS, codename jammy
- I installed Docker Engine
- Diagnostics ID: b6e8014b-6dfa-4582-84cd-a09db80f8c02/20230411082943
Expected behavior
Normal running of Docker Desktop
Actual behavior
Docker Desktop gives a message that docker engine stopped
But the Docker engine works normally:
Information
- Linux distro: Ubuntu 22.04.1 LTS
- Distro version: 22.04, codename jammy
- Docker Desktop Version: 4.18.0
Steps to reproduce the behavior
- Install docker engine
- Install and run docker desktop
The text was updated successfully, but these errors were encountered:
VasKonstV commented Apr 11, 2023
I made self diagnostics and the result is following:
VasKonstV commented Apr 11, 2023 •
VasKonstV commented Apr 11, 2023
And finally I tried to do the following:
modprobe kvm
And I got an Error:
modprobe: ERROR: could not insert ‘kvm’: Operation not permitted
VasKonstV commented Apr 11, 2023
And finally my self-diagonstics: 
VasKonstV commented Apr 11, 2023
And and several warnings:
1 : The check: is the credentials store configured correctly?
Produced the following warning: Error: password store is empty. Try «pass init».
The Credential Store is not set up correctly.
2 : The check: are KVM user permissions configured?
Produced the following warning: user must be added to the kvm group to access the kvm device, see https://docs.docker.com/desktop/install/linux-install/#kvm-virtualization-support
To start Docker Desktop, user must have access to the KVM device.
3 : The check: does the host support virtualization?
Produced the following warning: stat /dev/kvm: no such file or directory
The Docker engine runs inside a Linux VM. Therefore the host must support virtualization.
Check that hardware-assisted virtualization (either Intel VMX or AMD SVM) and Data Execution Prevention (sometimes labeled XD or Execute Disable or NX) are enabled in your BIOS.
Check your bootloader is configured to launch Hyper-V.
4 : The check: are KVM user permissions configured?
Produced the following warning: user must be added to the kvm group to access the kvm device, see https://docs.docker.com/desktop/install/linux-install/#kvm-virtualization-support
To start Docker Desktop, user must have access to the KVM device.
5 : The check: does the host support virtualization?
Produced the following warning: stat /dev/kvm: no such file or directory
The Docker engine runs inside a Linux VM. Therefore the host must support virtualization.
Check that hardware-assisted virtualization (either Intel VMX or AMD SVM) and Data Execution Prevention (sometimes labeled XD or Execute Disable or NX) are enabled in your BIOS.
Check your bootloader is configured to launch Hyper-V.
6 : The check: can a VM be started?
Produced the following warning: vm has not started: failed to open kmsg.log: open /home/vaskonst/.docker/desktop/log/vm/kmsg.log: no such file or directory
The Docker engine runs inside a Linux VM. Therefore we must be able to start Virtual Machines.
7 : The check: is the LinuxKit VM running?
Produced the following warning: vm is not running: failed to open kmsg.log: open /home/vaskonst/.docker/desktop/log/vm/kmsg.log: no such file or directory
The Docker engine runs inside a Linux VM. Therefore the VM must be running.
8 : The check: are the LinuxKit services running?
Produced the following warning: failed to ping VM diagnosticsd with error: Get «http://ipc/ping»: dial unix diagnosticd.sock: connect: no such file or directory
The Docker engine runs inside a Linux VM as a service. Therefore the services must have started.
9 : The check: is the Docker engine running?
Produced the following warning: Get «http://ipc/docker»: dial unix lifecycle-server.sock: connect: no such file or directory
The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.
10 : The check: does the Docker API work?
Produced the following warning: Cannot connect to the Docker daemon at unix://docker.raw.sock. Is the docker daemon running?
If the Docker API is not available from the host then Docker Desktop will not work correctly.
11 : The check: do Docker networks overlap with host IPs?
Produced the following warning: Cannot connect to the Docker daemon at unix://docker.raw.sock. Is the docker daemon running?