'Docker Failed to Initialize on Windows

Here, I have problem regarding pulling docker-dev in docker image for making my development environment but when I tried to pull docker-dev. I got the error like docker manifest not found. Can anyone help me out with this error...plz

before this I want to know about the docker failed to initialize error which i'm having right now...

the error is like,

I tried so many things like re-install the docker desktop or WSL updates, but didn't worked.

And error in the command be like... So if someone can help me out with this....plz help me out

docker docker-for-windows

Solution 1:^[1]

Got the same issue and fixed it by deleting %appdata%\Docker as mentioned by Github User "tocklime"

(Original Source : https://github.com/docker/for-win/issues/3088)

Solution 2:^[2]

My solution: delete %appdata%\Docker\settings.json and let Docker to create a new one.

Take a backup of the file for the next time it gets broken.

<tl;dr>

I face this issue almost every month and I hope this will get fixed definitely.

Following tmBlackCape answer, I checked the %appdata%\Docker directory and found settings.json damaged (editor tells it's a binary file and of course it shouldn't).

I deleted the file and Docker Service (still running) created a new one with default values. If the service isn't running, just launch it again.

You could need to change settings (via GUI, as recommended) to catch your needs.

I made a backup copy of my custom settings.json so next time I can replace the broken one without losing custom configuration.

Solution 3:^[3]

Go to the directory C:\Users-------\AppData\Roaming\Docker and delete the file settings.json . Docker takes care of rewriting it at startup.

This manipulation solved the problem for me !

Solution 4:^[4]

Docker failed to initialize

C:\Users[USER]\AppData\Local\Docker

C:\Users[USER]\AppData\Roaming\Docker

C:\Users[USER]\AppData\Roaming\Docker Desktop

Once deleted above directory, I didn’t have to do anything else, Docker Desktop started booting up as normal.

Solution 5:^[5]

This happened to me after Docker Desktop upgrade to version 3.6.0 (67351), too. (Which was surprising, because it worked before the upgrade.)

Due to the help in the top answer right now, I went to the above settings directory: %appdata%\Docker, looked at the logs and deleted/renamed the file settings.json -> Docker Desktop started immediatelly ; there had been a process retrying in the background.

In the time before that, the backend.exe.log had been all "unmarshal" something something:

    settings.json: json: cannot unmarshal bool into Go struct field Content.proxyHttpMode of type string"
common/cmd/com.docker.backend/internal/settingsloader.GetSettings(0x0, 0x0, 0x0)

So, the above message 'tipped me off' as to where the actual error on start may be. Hmm...

Solution 6:^[6]

For me deleting the folder %appdata%\Docker did not work.

Instead I had to run the following power shell command as admin.

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

References.

My windows features with running docker desktop are as follows.

Solution 7:^[7]

For me the solutions here didn't help, but here's what helped.

Make sure the folder .docker/ in your home directory isn't marked as hidden in Windows. If it's hidden, Docker won't see it.
Make sure docker has Active Directory to .docker folder. For example, if the owner of .docker/ is SYSTEM and not your user, Docker won't be able to read it and crash.

Solution 8:^[8]

Go to C:\Users\asd\AppData\Local and delete Downloaded Installation directory.
C:\Users\asd\AppData\Roaming and delete Docker and Docker Desktop directory.

Then start docker.

Solution 9:^[9]

Didn't found the AppData folder in users[myUser] or anywhere. re-install solve it for me

Solution 10:^[10]

It happened due to local data corruption. You can check in VM log inside %appdata%\Docker. I was able to reset and restart by renaming setting.json and then restart the Docker desktop by deleting all the previous log folder and temp folder clean. If this does not help. Try to kill all the processes running in through the task manager

and then run Power shell in administrator mode and then shoot the command if you are using an older version of Lsmanager Restart-Service LxssManager.

Solution 11:^[11]

On my side, uninstalling HyperV did the trick :

Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor

I also (as suggested in the voted answer):

Uninstalled docker desktop,
Deleted any docker related content in %APPDATA% as suggested
Delete any docker related keyys in registry (may be not necessary)
Then reinstalled it

And it solved the problem (but without hyperV removal it didn't work).

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source
Solution 1	srk
Solution 2	nessunluogo
Solution 3	IDIR
Solution 4	ÃŸÃ£lÃ£jÃ®
Solution 5
Solution 6	VivekDev
Solution 7
Solution 8	chintan bhatt
Solution 9	Itay Tur
Solution 10
Solution 11	FiNaLsPY

'Docker Failed to Initialize on Windows

Solution 1:[1]

Solution 2:[2]

Solution 3:[3]

Solution 4:[4]

Solution 5:[5]

Solution 6:[6]

Solution 7:[7]

Solution 8:[8]

Solution 9:[9]

Solution 10:[10]

Solution 11:[11]