- [x ] I have tried with the latest version of Docker Desktop
- I have tried disabling enabled experimental features
- I have uploaded Diagnostics
- Diagnostics ID:
Actual behavior
When running the application upon starting the docker desktop app, it shows me the error as mentioned in the subject and it doesnt start.
Expected behavior
Should start running upon opening the application.
Information
- Windows Version:
- Docker Desktop Version: 21h1 (OS BUILD 19043.1165)
- WSL2 or Hyper-V backend?
Enabled - Are you running inside a virtualized Windows e.g. on a cloud server or a VM:
Not
Log
[08:30:52.220][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[08:30:52.527][IPCClient ][Info ] (5c1e7562) 8fa11c3c-GoBackendClient-CSharp C->S BackendAPI GET /ping
[08:30:52.527][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[08:30:52.829][IPCClient ][Info ] (ef48f141) 8fa11c3c-GoBackendClient-CSharp C->S BackendAPI GET /ping
[08:30:52.829][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[08:30:53.134][IPCClient ][Info ] (65b865ae) 8fa11c3c-GoBackendClient-CSharp C->S BackendAPI GET /ping
[08:30:53.134][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[08:30:53.453][IPCClient ][Info ] (407e7f0b) 8fa11c3c-GoBackendClient-CSharp C->S BackendAPI GET /ping
[08:30:53.453][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[08:30:53.765][IPCClient ][Info ] (5eb08221) 8fa11c3c-GoBackendClient-CSharp C->S BackendAPI GET /ping
[08:30:53.765][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[08:30:54.067][IPCClient ][Info ] (aa9cb83b) 8fa11c3c-GoBackendClient-CSharp C->S BackendAPI GET /ping
[08:30:54.067][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[08:30:54.380][IPCClient ][Info ] (eaec7f63) 8fa11c3c-GoBackendClient-CSharp C->S BackendAPI GET /ping
[08:30:54.380][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[08:30:54.693][IPCClient ][Info ] (8f125368) 8fa11c3c-GoBackendClient-CSharp C->S BackendAPI GET /ping
[08:30:54.693][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[08:30:55.008][IPCClient ][Info ] (b2e7f848) 8fa11c3c-GoBackendClient-CSharp C->S BackendAPI GET /ping
[08:30:55.008][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[08:30:55.321][IPCClient ][Info ] (92c48810) 8fa11c3c-GoBackendClient-CSharp C->S BackendAPI GET /ping
[08:30:55.321][GoBackendClient ][Warning] HttpOS Client: connection timed out.
This is one of the headbanging issues when docker stops working with the error as per image -1
Solution:
Go to
C:\Users\{username}\AppData\Local\Docker
C:\Users\{username}\AppData\Roaming\Docker
C:\Users\{username}\AppData\Roaming\Docker Desktop
I have made the username bold as it should be different for you as shared mine
Delete all those docker folders or rename them.
Then open Docker as run as administrator, It should create fresh folders and open smoothly without any error.
Or by any chance, it throws an error, try uninstalling the Docker and delete the folders from the Program Files folder too, as mentioned below. then download and install a specific version of docker required.
Get inside
C:\Program Files
C:\ProgramData
C:\Program Files (x86)
Delete those docker folders or rename them.
After following the above steps, You should be able to run docker smoothly.
issue:
I found my docker brake down after upgrading docker to 20.10.8.
when I open docker desktop it shows: Docker Desktop is shutting down.
and shows error message when you run docker command
> docker ps > error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.25/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.
solution:
- open explorer and delete below folders to reset docker config
C:\Users[USER]\AppData\Local\Docker
notice: backup this folder to other location. it would be helpful to restore later.C:\Users[USER]\AppData\Roaming\Docker
C:\Users[USER]\AppData\Roaming\Docker Desktop
- and you would found your docker desktop can be start but showing starting forever
- run commands in PowerShell: notice: those commands would remove all containers/images in existing docker system if you don’t do a backup in previous steps.
wsl --unregister docker-desktop
wsl --unregister docker-desktop-data
- reboot system
- copy file
{backup-location}\wsl\data\ext4.vhdx
in step1.1 toC:\Users[USER]\AppData\Local\Docker\wsl\data\ext4.vhdx
- open docker desktop. it just come back and not data lost.
environment:
os=windows 10 pro 20H2
docker=20.10.8
refs:
- https://forums.docker.com/t/docker-failed-to-initialize/111341/14
- https://stackoverflow.com/questions/43041331/docker-forever-in-docker-is-starting-at-windows-task
- https://stackoverflow.com/questions/62380124/where-docker-image-is-stored-with-docker-desktop-for-windows
- Author
- Recent Posts
I started writing code around 20 years ago, and throughout the years, I have gained a lot of expertise from hands-on experience as well as learning from others. This website has also grown with me and is now something that I am proud of.
The Docker failed to initialize 2022 because your main document contains irrelevant data confusing your application and blocking the Docker desktop. On the flip side, we experienced an identical start Docker code exception when Docker failed to initialize wsl2 because the machine did not document the changes to the official site correctly.
To overcome this challenge, we researched the Docker container, located the failed inputs, and found the most sophisticated debugging approaches that will help you as well to overcome the Docker desktop failed to initialize Windows 10. In addition, we will exemplify why Docker failed using real-life scripts and syntaxes to help you troubleshoot the document and reenable the Docker download function.
JUMP TO TOPIC
- Why Is the Docker Failed to Initialize Error Happening?
- – Installing and Launching the Latest Docker Update
- – Disabling the Experimental Docker Features
- How To Fix the Docker That Failed to Initialize? Our Recommendations
- – Deleting the JSON Settings File
- Conclusion
The Docker failed to initialize Docker desktop is shutting down Windows 11 error is happening because your primary document has irrelevant data and files. As a result, you cannot install Docker community editor for Windows. Although the installation was successful, most of your commands are not fully functional.
For instance, this code exception happens when the program introduces new files after installation, which should not occur with bug-free applications. As a result, Docker failed to initialize Docker desktop is shutting down, confirming the document’s inconsistencies and broken data.
Unfortunately, this is one of the many culprits for the Docker mistake because the bug can also happen due to incorrect locations of the JSON files. Although this rarely happens, it can confuse your program and force the code exception confirming Docker failed to initialize Docker desktop is already running.
On the flip side, this bug is sometimes challenging to pinpoint and fix because the installation does not indicate any issues or errors. In addition, the message box tells you to log out and log in after completing the installation, which is logical because the program must save the changes before running its properties.
As a result, we wrote several chapters to help you clear these inconsistencies and repair your document without affecting other operations and procedures. You will also learn how to scan your script for the Docker failed to initialize Docker desktop is shutting down Windows 10 code exception before applying the debugging methods.
– Installing and Launching the Latest Docker Update
We confirmed that this Docker bug will almost always happen when installing and launching the latest update because the program creates new files. Unfortunately, some systems face challenges recognizing the inputs and rendering the data, forcing your program to display the exception. As a result, we will exemplify the installation log providing more information on the new documents.
The following example provides the entire installation log:
Sha1: eb84a71876f14fe31a1i856896cb8b137e6e541763
Started on: 2022/11/30 08:34:58.342
Resources: C:\Program Files\Docker\Docker\resources
OS: Windows 11 Pro
Edition: Professional
Build: 12595
CommandLine: “C:\Program Files\Docker\InstallerCli.exe” -k -p
You can send feedback, including this log file, at https://github.com/docker/for-win/issues
[08:34:58.712][Installer ][Info ] Killing existing com.docker.service process with PID 6304
[08:34:59.502][Installer ][Info ] Preparing upgrade…
[08:34:59.695][HyperV ][Warning] Hyper-V is not installed on the machine
[08:35:00.120][LinuxWSL2Engine ][Info ] Debian: found credsStore with desktop.exe, rewriting
[08:35:00.190][Installer ][Info ] Prepare upgrade completed successfully
[08:35:00.190][Installer ][Info ] Fixing permissions…
[08:35:00.191][Installer ][Info ] Deleting directory C:\Program Files\Docker\cli-plugins
[08:35:00.192][Installer ][Info ] removing permission inheritance from C:\ProgramData\DockerDesktop
[08:35:00.193][Installer ][Info ] removing ACLs except for SYSTEM and Administrators from C:\ProgramData\DockerDesktop
[08:35:00.194][Installer ][Info ] removing permission inheritance from C:\Program Files\Docker\cli-plugins
[08:35:00.195][Installer ][Info ] removing ACLs except for SYSTEM and Administrators from C:\Program Files\Docker\cli-plugins
[08:35:00.196][Installer ][Info ] granting ReadAndExecute to everyone for C:\Program Files\Docker\cli-plugins
[08:35:00.198][Installer ][Info ] removing permission inheritance from C:\ProgramData\Docker
[08:35:00.200][Installer ][Info ] removing ACLs except for SYSTEM and Administrators from C:\ProgramData\Docker
[08:35:00.210][Installer ][Info ] granting ReadWriteDelete to authenticated users for C:\ProgramData\Docker\config
As you can tell, this exception is filled with flaws and inconsistencies, ruining your programming experience and halting further procedures. Still, this is one of the few culprits for this persistent bug.
– Disabling the Experimental Docker Features
Your application encounters this exception, although disabling the experimental Docker features confuses the system. In addition, we tried updating the latest Docker version to prevent the error, which was all in vain because the machine installed the files blocking your program from the former chapter. As a result, check the output of your Docker executable file to locate inconsistencies and flaws.
The following example provides the output:
[SKIP] DD0028: is there available VM disk space?
[FAIL] DD0031: does the Docker API work? error during connect: This error indicates that the docker daemon is not running.: Get “http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/v1.24/containers/json?limit=0”: open //./pipe/docker_engine_linux: The system cannot find the file specified.
[PASS] DD0016: is the LinuxKit VM running?
[FAIL] DD0001: is the application running? Docker is not running
[PASS] DD0017: can a VM be started?
[PASS] DD0024: is WSL installed?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? exit status 0xffffffff
[FAIL] DD0035: is the VM time synchronized? exit status 0xffffffff
[FAIL] DD0003: is the Docker CLI working? exit status 1
[PASS] DD0013: is the $PATH ok?
[FAIL] DD0007: is the backend responding? failed to ping com.docker.backend with error: Get “http://ipc/ping”: open \\.\pipe\dockerBackendApiServer: The system cannot find the file specified.
2022/07/19 15:49:06 exit status 0xffffffff
You must not avoid this critical troubleshooting step because you will learn more about the error’s cause. Hence, you can take action quickly and reenable your program.
How To Fix the Docker That Failed to Initialize? Our Recommendations
You can fix the docker that failed to initialize error by deleting the irrelevant Docker files that are confusing your program. The roaming data installed by the latest Docker upgrade will clear all inconsistencies. Alternatively, you can fix it by executing a specific command and starting the Docker services.
Although deleting the Docker files is the fastest debugging approach for this dynamic mistake, it is not the only one. Hence, we will teach you how to execute the program files command to initiate the debugging approach. Later, you must mess around with the Service Configuration Panel settings.
We suggest introducing the following command line:
C:\ Users\ Administrator > cd \
C:\ > cd “Program Files”
C:\ Program Files > cd Docker
C:\ Program Files\ Docker > cd Docker
C:\ Program Files\ Docker\ Docker > DockerCli.exe -SwitchDaemon
C:\ Program Files\ Docker\ Docker>
This brief procedure pinpoints and starts the debugging operation by providing the correct locations. As you can tell, you can find critical data about Docker in your Program Files. This data is vital when restarting the Docker services. However, the solution is only complete after making changes to the Service Configuration Panel.
Namely, navigate and stop the Docker service in the Service Configuration Panel. This ensures the program renders the changes made by the former code snippet. Then, you must restart the Docker service to launch the program and complete the solution. Luckily, this method does not mess up other functions and commands.
– Deleting the JSON Settings File
As formerly explained, you can get around this mistake by deleting the latest Docker files in your document. You can quickly locate the JSON settings file because it exists in the same Docker folder. Although the location is different for each system, you can typically find it in the User’s home and an additional Docker path. Alternatively, you can pinpoint the JSON settings file with a similar pattern.
However, after deleting the specific file, you must restart the system to complete and save the changes on your machine. This ensures the program renders all inputs without issues or mistakes. Lastly, you can run the Docker desktop application after restarting your computer and saving the changes. The error will disappear, and you can finally enjoy your programming experience.
Conclusion
The Docker failed to initialize because your main document contains irrelevant data confusing your application and blocking the desktop application. So, let us remember this article’s critical points in the following bullet list:
- The mistake can happen when the machine does not document the changes to the official site correctly
- The latest Docker update installs several incorrect files
- Deleting the irrelevant Docker files removes the exception and fixes your project
- The alternative debugging approach suggests messing around with the Service Configuration Panel settings
Experiencing this mistake after applying the debugging methods is unlikely, especially with simple applications. So, open your forgotten project, apply the solutions, and complete your application.
- Why is my Docker Desktop failed to start?
- How long does Docker desktop take to start?
- Why is my Docker not running?
- Why is Docker not working Windows 10?
- What is Docker daemon?
- Where is my Docker daemon running?
- How do I stop Docker from running on Windows?
- Do you need Docker desktop?
- What does Docker restart do?
Why is my Docker Desktop failed to start?
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.
How long does Docker desktop take to start?
Post Graduate Program in DevOps
Enables integrated user interface to view and monitor Docker containers. Quickly starts Docker within ten seconds.
Why is my Docker 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.
Why is Docker not working Windows 10?
If virtualization is disabled Docker Desktop cannot start. If the virtualization is disabled in your machine then you need to enable it from BIOS Settings. Note that Windows 10 Home edition doesn’t support Hyper-V feature only Windows 10 Enterprise, Pro, or Education support it.
What is Docker daemon?
The Docker daemon ( dockerd ) listens for Docker API requests and manages Docker objects such as images, containers, networks, and volumes. A daemon can also communicate with other daemons to manage Docker services.
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.
How do I stop Docker from running on Windows?
Stopping a Container Using Process Signals
With the docker run command’s —stop-signal flag, you can specify the stop signal when starting the container. This flag sets the signal that will be sent to the running container when you want it to stop.
Do you need Docker desktop?
Yes. Commercial use of Docker Desktop at a company of more than 250 employees OR more than $10 million in annual revenue requires a paid subscription (Pro, Team, or Business) to use Docker Desktop.
What does Docker restart do?
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.