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
BMitch
214k40 gold badges455 silver badges427 bronze badges
asked Jun 23, 2021 at 8:44
4
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)
srk
4,73812 gold badges62 silver badges108 bronze badges
answered Jun 30, 2021 at 11:57
tmBlackCapetmBlackCape
1,6141 gold badge4 silver badges2 bronze badges
8
Short solution: delete %appdata%Dockersettings.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.
answered Aug 5, 2021 at 7:50
nessunluogonessunluogo
4503 silver badges8 bronze badges
3
Go to the directory C:Users——-AppDataRoamingDocker and delete the file settings.json . Docker takes care of rewriting it at startup.
This manipulation solved the problem for me !
answered Oct 5, 2021 at 10:17
IDIRIDIR
3312 silver badges4 bronze badges
Docker failed to initialize
C:Users[USER]AppDataLocalDocker
C:Users[USER]AppDataRoamingDocker
C:Users[USER]AppDataRoamingDocker Desktop
Once deleted above directory, I didn’t have to do anything else, Docker Desktop started booting up as normal.
answered Oct 2, 2021 at 5:10
BalajiBalaji
8,4975 gold badges41 silver badges45 bronze badges
The error message I got was not exactly the same the OP got. For me, it said Docker failed to initialize. Docker Desktop is shutting down.
TL;DR
The powershell executable was missing from my local machies PATH. I had to add C:WindowsSystem32WindowsPowerShellv1.0 and docker started again.
The longer story
I tried everything that was mentined in this thread and nothing worked for me. When I looked at the task manager of my local machine to see if any docker-related process was started, I noticed that Docker Desktop.exe itself was started. However, the com.docker.backend.exe not. Docker tries to start that exe in an infinite loop, but as soon as it started it crashed again after half a second.
I then took a look into com.docker.backend.exe.log, which is located in %localappdata%Dockerloghost and noticed the following line:
[2022-07-07T10:46:57.936079700Z][com.docker.backend.exe][F] exec: "powershell": executable file not found in %PATH%
I then went ahead and just added the path to powershell to PATH (which is C:WindowsSystem32WindowsPowerShellv1.0)`. As soon as I added that, everything started working again.
I have no idea how the path to the powershell executable got removed from PATH. I certainly did not do that myself.
answered Jul 7, 2022 at 11:12
MikeVeMikeVe
8628 silver badges12 bronze badges
3
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…
answered Aug 18, 2021 at 18:35
Jordan GeeJordan Gee
3703 silver badges10 bronze badges
1
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
.dockerfolder. For example, if the owner of.docker/isSYSTEMand not your user, Docker won’t be able to read it and crash.
answered Mar 2, 2022 at 13:01
DanonDanon
2,54425 silver badges37 bronze badges
1
It resolved me by deleting the file
C:Users{username}AppDataRoamingDockersettings.json
answered Jun 21, 2022 at 17:37
2
I had the same issue. I’m on Docker Desktop 4.8.0. The following solution worked for me:
- Uninstall Docker Desktop
- Delete .docker folder from
C:Users{Username} - Delete Docker folder from
C:Users{Username}AppDataLocal - Delete Docker folder from
C:Users{Username}AppDataRoaming - Delete Docker folder from
C:Program Files - Run CCleaner on Registry and Custom Clean
- Restart Computer
- Install Docker
- Restart Computer
- Start Docker
That’s all.
answered Sep 27, 2022 at 23:13
Navneil NaickerNavneil Naicker
3,5162 gold badges21 silver badges31 bronze badges
- Go to C:UsersasdAppDataLocal and delete Downloaded Installation directory.
- C:UsersasdAppDataRoaming and delete Docker and Docker Desktop directory.
Then start docker.
answered Oct 13, 2021 at 7:24
Didn’t found the AppData folder in users[myUser] or anywhere. re-install solve it for me
answered Nov 6, 2021 at 14:39
Itay TurItay Tur
4331 gold badge14 silver badges32 bronze badges
latest update 4.10.1 has issues, i downgraded to 4.6.1 and it worked however i think powershell is closely linked to this issue
answered Jul 20, 2022 at 7:41
1
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.
answered Mar 24, 2022 at 6:43
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).
answered Apr 11, 2022 at 9:18
There are a few great solutions; however, it didn’t work for me. Most of the «fixes» suggested here are already implemented and it just didn’t work. I chose a different approach.
I looked at the docker releases and saw what was actually affected by their latest version not working (4.10). These things are normal, especially if the software engine has been updated.
Going through Docker releases, the latest release that didn’t touch the Docker engine is 4.8.0. I downloaded and works great.
answered Jul 17, 2022 at 21:25
Removing settings.json file or %AppData%Docker folder did not work for me. After uninstalling/installing the docker, the issue was solved. (Note: I couldn’t try other possible solutions that are required the admin privilege)
answered Sep 1, 2022 at 14:55
burak isikburak isik
3354 silver badges6 bronze badges
The below Steps worked for me,
Step 01:
Navigate to the below-mentioned paths and delete the below-mentioned directories,
C:Users[USERNAME]AppDataLocalDocker directory
C:Users[USERNAME]AppDataRoamingDocker directory
C:Users[USERNAME]AppDataRoamingDocker Desktop directory
Then restart the docker again
If you didn’t find the AppData folder in users[USERNAME] or anywhere
Step 02: Type the below path in the «Run» to directly open the app data location for you
%appdata%Docker
Then Delete the below-mentioned directories,
C:Users[USERNAME]AppDataLocalDocker directory
C:Users[USERNAME]AppDataRoamingDocker directory
C:Users[USERNAME]AppDataRoamingDocker Desktop directory
Then restart the docker again
Note: If these steps do not help you. Try to kill all the processes running in through the task manager. And again delete the directories and start the docker
answered Sep 9, 2022 at 6:23
if you still can’t find the issue you may use this trick and i’m 100% sure this will work
first check your operating system is up to date means no remaining updates if you pass this step then come to 2 step open window command prompt in run as administrator
then type wsl —install then type wsl —list —online then wsl —install -d Debian
then open docker if error come
then install wsl 2 linux https://learn.microsoft.com/en-us/windows/wsl/install-manual#step-4—download-the-linux-kernel-update-package
then restart docker or your machine and then if error also occur then type then wsl —update i hope this will work Regard : Hammad Khadim
answered Oct 20, 2022 at 22:02
- I have tried with the latest version of Docker Desktop
- I have tried disabling enabled experimental features
- I have uploaded Diagnostics
- Diagnostics ID: B5B38B36-3D53-46EC-9E95-46959232F6F2/20210804030845 (Docker Desktop 3.5.2)
- Diagnostics ID: B5B38B36-3D53-46EC-9E95-46959232F6F2/20210804020912 (Docker Desktop 3.5.1)
Actual behavior
Can’t initialize Docker Desktop, Docker Desktop prompt the figure below:
Expected behavior
Docker Desktop runs normally
Information
- Windows Version: Windows 10 HOME 64-bit (10.0, Build 19042)
- Docker Desktop Version: 3.5.2 (66501)
- WSL2 or Hyper-V backend? WSL2
- Are you running inside a virtualized Windows e.g. on a cloud server or a VM: WSL2 — Ubuntu 20.04 LTS
Steps to reproduce the behavior
- I had had this issue since Docker Desktop
3.5.1, I uninstall then re- install the latest version of Docker Desktop3.5.2then run diagnose again. - According to the issue Docker failed to intialize #11273 and Failed to start docker desktop for windows 10 Enterprise! Crashing, error show issue with BackgroundUpdateWatcher. #11745, I re-checked
Background Intelligent Transfer Service. It didn’t run when I checked. I enabled it but the Docker still could not start.
Below is the error log file:
Version: 3.5.2 (66501)
Sha1: 84e4b4334c1e4ea66e074cf2d17440e1f62ab201
Started on: 2021/08/04 10:08:31.566
Resources: C:Program FilesDockerDockerresources
OS: Windows 10 Home
Edition: Core
Id: 2009
Build: 19042
BuildLabName: 19041.1.amd64fre.vb_release.191206-1406
File: C:UserslongqAppDataLocalDockerlog.txt
CommandLine: "C:Program FilesDockerDockerDocker Desktop.exe"
You can send feedback, including this log file, at https://github.com/docker/for-win/issues
[10:08:31.650][GUI ][Info ] Starting...
[10:08:31.673][GUI ][Warning] Failed to configure docker scan: Newtonsoft.Json.JsonSerializationException: No JSON content found. Path '', line 1, position 72.
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Populate(JsonReader reader, Object target)
at Newtonsoft.Json.JsonSerializer.PopulateInternal(JsonReader reader, Object target)
at Newtonsoft.Json.JsonConvert.PopulateObject(String value, Object target, JsonSerializerSettings settings)
at Docker.Core.Cli.ScanOptionsLoader.Configure(String snykPath) in C:workspacesPR-16070srcgithub.comdockerpinatawinsrcDocker.CorecliScanOptionsLoader.cs:line 18
at Docker.Program.CheckDockerScanConfigFile(Logger logger) in C:workspacesPR-16070srcgithub.comdockerpinatawinsrcDocker.DesktopProgram.cs:line 144
[10:08:31.853][GUI ][Info ] An instance is already running. Launching the container view.
[10:08:31.889][GUI ][Error ] System.TimeoutException:
The operation has timed out.
at System.IO.Pipes.NamedPipeClientStream.ConnectInternal(Int32 timeout, CancellationToken cancellationToken, Int32 startTime)
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at HttpOverStream.NamedPipe.NamedPipeDialer.<DialAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at HttpOverStream.Client.DialMessageHandler.<SendAsync>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Net.Http.HttpClient.<FinishSendAsyncBuffered>d__58.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Docker.Program.Run(IReadOnlyCollection`1 args) in C:workspacesPR-16070srcgithub.comdockerpinatawinsrcDocker.DesktopProgram.cs:line 196
[10:08:31.946][IPCClient ][Info ] (9f844e66) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:31.946][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:32.253][IPCClient ][Info ] (c4d15fce) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:32.253][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:32.313][GoBackendProcess ][Error ] Auto restarting process
[10:08:32.313][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:08:32.315][GoBackendProcess ][Info ] Started
[10:08:32.375][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:08:32.387][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:08:32.391][GoBackendProcess ][Error ] Process died
[10:08:32.565][IPCClient ][Info ] (4b92cadf) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:32.565][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:32.867][IPCClient ][Info ] (370350fb) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:32.867][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:33.169][IPCClient ][Info ] (d73c55bd) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:33.169][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:33.483][IPCClient ][Info ] (1482b2dd) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:33.483][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:33.793][IPCClient ][Info ] (4d87a205) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:33.793][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:34.095][IPCClient ][Info ] (087fa22f) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:34.095][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:34.408][IPCClient ][Info ] (3854402a) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:34.408][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:34.717][IPCClient ][Info ] (ce79c1a5) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:34.717][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:35.030][IPCClient ][Info ] (3a5d2d0f) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:35.030][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:35.342][IPCClient ][Info ] (58b2a5a2) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:35.342][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:35.654][IPCClient ][Info ] (300ebfec) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:35.654][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:35.965][IPCClient ][Info ] (9ad8685a) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:35.965][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:36.266][IPCClient ][Info ] (74d6e7b2) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:36.266][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:36.574][IPCClient ][Info ] (aa4d061e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:36.574][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:36.884][IPCClient ][Info ] (ac85d939) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:36.884][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:37.197][IPCClient ][Info ] (c18694ba) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:37.197][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:37.398][GoBackendProcess ][Error ] Auto restarting process
[10:08:37.398][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:08:37.400][GoBackendProcess ][Info ] Started
[10:08:37.461][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:08:37.472][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:08:37.476][GoBackendProcess ][Error ] Process died
[10:08:37.507][IPCClient ][Info ] (c9b10073) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:37.507][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:37.818][IPCClient ][Info ] (4b8de3fe) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:37.819][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:38.127][IPCClient ][Info ] (5b87411b) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:38.127][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:38.438][IPCClient ][Info ] (07b3b6f6) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:38.438][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:38.750][IPCClient ][Info ] (56c995d8) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:38.750][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:39.060][IPCClient ][Info ] (8b4e973d) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:39.060][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:39.370][IPCClient ][Info ] (0bfb83ae) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:39.370][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:39.679][IPCClient ][Info ] (e8391163) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:39.679][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:39.989][IPCClient ][Info ] (870746da) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:39.989][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:40.302][IPCClient ][Info ] (1f576dbd) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:40.302][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:40.614][IPCClient ][Info ] (0fb7d2bf) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:40.614][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:40.929][IPCClient ][Info ] (eb22e0f5) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:40.929][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:41.242][IPCClient ][Info ] (0aa58cdb) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:41.242][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:41.552][IPCClient ][Info ] (b972f46a) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:41.552][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:41.861][IPCClient ][Info ] (3bd86015) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:41.861][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:42.174][IPCClient ][Info ] (ef8550a6) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:42.174][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:42.487][GoBackendProcess ][Error ] Auto restarting process
[10:08:42.487][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:08:42.487][IPCClient ][Info ] (b34efa87) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:42.487][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:42.489][GoBackendProcess ][Info ] Started
[10:08:42.549][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:08:42.561][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:08:42.566][GoBackendProcess ][Error ] Process died
[10:08:42.796][IPCClient ][Info ] (c9a237c9) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:42.797][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:43.108][IPCClient ][Info ] (4285ef3c) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:43.108][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:43.416][IPCClient ][Info ] (5bf959c0) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:43.416][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:43.728][IPCClient ][Info ] (2532d26c) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:43.728][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:44.038][IPCClient ][Info ] (f664912e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:44.038][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:44.350][IPCClient ][Info ] (246feb1f) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:44.350][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:44.657][IPCClient ][Info ] (a5570de2) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:44.657][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:44.972][IPCClient ][Info ] (35b85dce) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:44.972][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:45.282][IPCClient ][Info ] (424e2106) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:45.282][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:45.592][IPCClient ][Info ] (75aabb2b) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:45.593][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:45.901][IPCClient ][Info ] (6024cd3e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:45.901][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:46.212][IPCClient ][Info ] (ae2dac87) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:46.212][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:46.526][IPCClient ][Info ] (2ef5bb91) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:46.526][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:46.833][IPCClient ][Info ] (aaec98c1) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:46.833][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:47.143][IPCClient ][Info ] (e2418b60) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:47.143][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:47.456][IPCClient ][Info ] (49ac9c60) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:47.456][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:47.579][GoBackendProcess ][Error ] Auto restarting process
[10:08:47.579][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:08:47.581][GoBackendProcess ][Info ] Started
[10:08:47.642][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:08:47.652][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:08:47.656][GoBackendProcess ][Error ] Process died
[10:08:47.765][IPCClient ][Info ] (0c993c29) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:47.765][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:48.078][IPCClient ][Info ] (e9acbf04) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:48.078][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:48.389][IPCClient ][Info ] (5da7ea48) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:48.389][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:48.699][IPCClient ][Info ] (e56ef06a) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:48.699][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:49.011][IPCClient ][Info ] (ee015369) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:49.011][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:49.324][IPCClient ][Info ] (734097f1) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:49.325][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:49.636][IPCClient ][Info ] (2e57e771) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:49.636][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:49.946][IPCClient ][Info ] (26a4fe23) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:49.946][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:50.255][IPCClient ][Info ] (1408380d) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:50.255][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:50.565][IPCClient ][Info ] (e3c6ba34) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:50.565][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:50.875][IPCClient ][Info ] (0aae22ac) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:50.875][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:51.183][IPCClient ][Info ] (c62511c4) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:51.183][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:51.493][IPCClient ][Info ] (34d73b9d) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:51.493][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:51.804][IPCClient ][Info ] (fb20cefd) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:51.804][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:52.113][IPCClient ][Info ] (45a741aa) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:52.113][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:52.424][IPCClient ][Info ] (1237dd32) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:52.424][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:52.661][GoBackendProcess ][Error ] Auto restarting process
[10:08:52.661][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:08:52.663][GoBackendProcess ][Info ] Started
[10:08:52.723][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:08:52.735][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:08:52.738][IPCClient ][Info ] (f9dbfc9b) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:52.738][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:52.738][GoBackendProcess ][Error ] Process died
[10:08:53.049][IPCClient ][Info ] (b8585aa7) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:53.049][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:53.361][IPCClient ][Info ] (6374763e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:53.361][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:53.675][IPCClient ][Info ] (c1224814) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:53.675][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:53.986][IPCClient ][Info ] (ab48b4f4) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:53.986][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:54.295][IPCClient ][Info ] (af361263) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:54.295][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:54.607][IPCClient ][Info ] (c739bbe3) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:54.607][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:54.918][IPCClient ][Info ] (57746d31) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:54.918][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:55.227][IPCClient ][Info ] (fe04eb75) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:55.227][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:55.538][IPCClient ][Info ] (7947c210) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:55.538][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:55.848][IPCClient ][Info ] (89a0f8a5) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:55.848][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:56.158][IPCClient ][Info ] (9529e68a) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:56.158][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:56.469][IPCClient ][Info ] (584b2b3d) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:56.469][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:56.778][IPCClient ][Info ] (9b517c97) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:56.778][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:57.087][IPCClient ][Info ] (d7a4970e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:57.087][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:57.400][IPCClient ][Info ] (0df8f772) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:57.400][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:57.714][IPCClient ][Info ] (1e692f92) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:57.714][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:57.746][GoBackendProcess ][Error ] Auto restarting process
[10:08:57.746][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:08:57.747][GoBackendProcess ][Info ] Started
[10:08:57.808][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:08:57.819][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:08:57.823][GoBackendProcess ][Error ] Process died
[10:08:58.025][IPCClient ][Info ] (aef03be4) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:58.025][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:58.336][IPCClient ][Info ] (cd9810d2) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:58.337][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:58.647][IPCClient ][Info ] (dae6e3f8) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:58.647][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:58.958][IPCClient ][Info ] (47cdd388) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:58.958][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:59.270][IPCClient ][Info ] (dad0a87c) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:59.270][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:59.579][IPCClient ][Info ] (24924a20) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:59.579][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:08:59.889][IPCClient ][Info ] (1d3d70ab) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:08:59.889][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:00.201][IPCClient ][Info ] (8444eb1e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:00.201][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:00.512][IPCClient ][Info ] (f639054e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:00.512][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:00.822][IPCClient ][Info ] (c61ec96b) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:00.823][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:01.136][IPCClient ][Info ] (2c9f8cff) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:01.136][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:01.447][IPCClient ][Info ] (d533af24) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:01.447][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:01.757][IPCClient ][Info ] (d51cc543) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:01.757][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:02.067][IPCClient ][Info ] (5381bb5d) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:02.067][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:02.067][SettingsLoader ][Warning] Failed to fetch settings from backend, retrying in 1 sec
[10:09:02.068][IPCClient ][Info ] (9223340f) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:02.068][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:02.378][IPCClient ][Info ] (1ad7b643) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:02.378][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:02.688][IPCClient ][Info ] (227200c9) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:02.688][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:02.829][GoBackendProcess ][Error ] Auto restarting process
[10:09:02.829][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:09:02.831][GoBackendProcess ][Info ] Started
[10:09:02.891][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:09:02.903][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:09:02.907][GoBackendProcess ][Error ] Process died
[10:09:02.998][IPCClient ][Info ] (5b32ca94) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:02.998][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:03.309][IPCClient ][Info ] (6a30732e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:03.309][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:03.618][IPCClient ][Info ] (21533f1a) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:03.618][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:03.927][IPCClient ][Info ] (dd776e46) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:03.927][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:04.238][IPCClient ][Info ] (88cd05ab) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:04.238][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:04.549][IPCClient ][Info ] (54b5e236) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:04.549][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:04.856][IPCClient ][Info ] (5ad25211) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:04.856][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:05.167][IPCClient ][Info ] (3f333703) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:05.167][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:05.476][IPCClient ][Info ] (dd41f9e4) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:05.476][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:05.785][IPCClient ][Info ] (a203b331) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:05.785][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:06.093][IPCClient ][Info ] (a05f8f96) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:06.093][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:06.400][IPCClient ][Info ] (9c4a280f) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:06.400][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:06.710][IPCClient ][Info ] (7229edef) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:06.710][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:07.019][IPCClient ][Info ] (08c34214) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:07.019][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:07.328][IPCClient ][Info ] (b5377a71) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:07.329][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:07.638][IPCClient ][Info ] (f2e7d627) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:07.638][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:07.917][GoBackendProcess ][Error ] Auto restarting process
[10:09:07.917][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:09:07.919][GoBackendProcess ][Info ] Started
[10:09:07.948][IPCClient ][Info ] (cbccc66f) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:07.949][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:07.980][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:09:07.992][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:09:07.996][GoBackendProcess ][Error ] Process died
[10:09:08.259][IPCClient ][Info ] (73b5631c) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:08.259][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:08.570][IPCClient ][Info ] (e4e92244) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:08.570][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:08.877][IPCClient ][Info ] (05d30f5c) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:08.877][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:09.188][IPCClient ][Info ] (e44ea9cf) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:09.188][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:09.500][IPCClient ][Info ] (d83e1611) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:09.500][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:09.810][IPCClient ][Info ] (eee3e364) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:09.810][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:10.117][IPCClient ][Info ] (da960df7) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:10.117][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:10.429][IPCClient ][Info ] (759fe080) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:10.429][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:10.738][IPCClient ][Info ] (cc03cfb1) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:10.738][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:11.048][IPCClient ][Info ] (ec512ac8) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:11.048][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:11.360][IPCClient ][Info ] (b49342e4) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:11.360][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:11.670][IPCClient ][Info ] (ee4d070c) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:11.670][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:11.979][IPCClient ][Info ] (883b277e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:11.979][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:12.288][IPCClient ][Info ] (7cc96b53) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:12.288][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:12.599][IPCClient ][Info ] (ab4ff622) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:12.599][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:12.909][IPCClient ][Info ] (1807c563) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:12.909][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:13.002][GoBackendProcess ][Error ] Auto restarting process
[10:09:13.002][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:09:13.004][GoBackendProcess ][Info ] Started
[10:09:13.063][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:09:13.074][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:09:13.078][GoBackendProcess ][Error ] Process died
[10:09:13.217][IPCClient ][Info ] (b27f7a9f) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:13.217][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:13.527][IPCClient ][Info ] (971b53a1) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:13.527][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:13.834][IPCClient ][Info ] (05721ba5) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:13.834][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:14.143][IPCClient ][Info ] (76ae2556) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:14.143][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:14.450][IPCClient ][Info ] (86e8e36e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:14.450][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:14.762][IPCClient ][Info ] (ed5a65c1) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:14.762][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:15.073][IPCClient ][Info ] (73e30f70) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:15.073][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:15.383][IPCClient ][Info ] (9a1f5114) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:15.383][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:15.692][IPCClient ][Info ] (5546fcc8) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:15.692][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:16.001][IPCClient ][Info ] (fc2fa1a8) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:16.001][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:16.312][IPCClient ][Info ] (8dbdcd48) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:16.312][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:16.621][IPCClient ][Info ] (9f04a90b) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:16.621][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:16.931][IPCClient ][Info ] (bb160ef8) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:16.931][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:17.242][IPCClient ][Info ] (3aaabae3) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:17.242][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:17.554][IPCClient ][Info ] (31d1c913) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:17.554][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:17.867][IPCClient ][Info ] (8cce3105) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:17.867][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:18.083][GoBackendProcess ][Error ] Auto restarting process
[10:09:18.083][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:09:18.085][GoBackendProcess ][Info ] Started
[10:09:18.146][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:09:18.158][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:09:18.163][GoBackendProcess ][Error ] Process died
[10:09:18.176][IPCClient ][Info ] (35cc6f4a) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:18.176][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:18.488][IPCClient ][Info ] (18a4af43) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:18.488][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:18.799][IPCClient ][Info ] (d7bd3dfa) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:18.799][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:19.108][IPCClient ][Info ] (e1a11c82) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:19.108][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:19.417][IPCClient ][Info ] (62181123) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:19.417][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:19.726][IPCClient ][Info ] (076c2103) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:19.726][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:20.038][IPCClient ][Info ] (3394a484) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:20.038][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:20.350][IPCClient ][Info ] (8145fccd) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:20.350][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:20.659][IPCClient ][Info ] (9998886e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:20.659][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:20.970][IPCClient ][Info ] (936be68f) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:20.970][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:21.279][IPCClient ][Info ] (6be70d5e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:21.279][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:21.590][IPCClient ][Info ] (7ff91d47) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:21.590][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:21.903][IPCClient ][Info ] (0374af2c) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:21.903][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:22.211][IPCClient ][Info ] (1353f9eb) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:22.211][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:22.522][IPCClient ][Info ] (5d4785bd) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:22.523][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:22.832][IPCClient ][Info ] (c304ffb5) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:22.832][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:23.142][IPCClient ][Info ] (5d6d7f8e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:23.142][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:23.172][GoBackendProcess ][Error ] Auto restarting process
[10:09:23.172][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:09:23.174][GoBackendProcess ][Info ] Started
[10:09:23.235][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:09:23.246][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:09:23.249][GoBackendProcess ][Error ] Process died
[10:09:23.451][IPCClient ][Info ] (d417820d) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:23.451][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:23.765][IPCClient ][Info ] (9b1c9332) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:23.765][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:24.078][IPCClient ][Info ] (acae93a6) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:24.078][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:24.389][IPCClient ][Info ] (33f24db3) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:24.389][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:24.699][IPCClient ][Info ] (f14d989a) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:24.699][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:25.010][IPCClient ][Info ] (8664da74) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:25.010][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:25.320][IPCClient ][Info ] (e2a0aaf1) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:25.320][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:25.630][IPCClient ][Info ] (9c3992d7) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:25.630][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:25.939][IPCClient ][Info ] (c7d806dd) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:25.939][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:26.250][IPCClient ][Info ] (15f40af0) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:26.250][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:26.558][IPCClient ][Info ] (8f01d900) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:26.558][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:26.866][IPCClient ][Info ] (9044f0a4) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:26.866][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:27.177][IPCClient ][Info ] (a734beba) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:27.177][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:27.487][IPCClient ][Info ] (07814b4e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:27.487][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:27.797][IPCClient ][Info ] (cb51b2b4) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:27.797][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:28.107][IPCClient ][Info ] (67afe2e3) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:28.107][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:28.265][GoBackendProcess ][Error ] Auto restarting process
[10:09:28.265][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:09:28.267][GoBackendProcess ][Info ] Started
[10:09:28.327][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:09:28.337][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:09:28.341][GoBackendProcess ][Error ] Process died
[10:09:28.419][IPCClient ][Info ] (af680c91) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:28.419][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:28.730][IPCClient ][Info ] (acf515a5) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:28.730][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:29.041][IPCClient ][Info ] (f4c29007) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:29.041][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:29.352][IPCClient ][Info ] (d5ee32f7) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:29.352][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:29.660][IPCClient ][Info ] (78bbb2d2) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:29.660][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:29.973][IPCClient ][Info ] (fb380f84) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:29.973][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:30.281][IPCClient ][Info ] (1c4fe757) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:30.281][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:30.591][IPCClient ][Info ] (1ccf8f1e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:30.591][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:30.899][IPCClient ][Info ] (15c477bc) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:30.899][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:31.210][IPCClient ][Info ] (987479e7) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:31.210][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:31.520][IPCClient ][Info ] (dcda8c99) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:31.521][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:31.830][IPCClient ][Info ] (ac433c17) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:31.830][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:32.140][IPCClient ][Info ] (5a2fd716) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:32.140][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:32.451][IPCClient ][Info ] (edc31a81) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:32.451][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:32.761][IPCClient ][Info ] (8c6c12d9) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:32.761][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:33.072][IPCClient ][Info ] (43c16ada) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:33.072][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:33.349][GoBackendProcess ][Error ] Auto restarting process
[10:09:33.349][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:09:33.351][GoBackendProcess ][Info ] Started
[10:09:33.380][IPCClient ][Info ] (c3ce1157) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:33.380][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:33.411][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:09:33.423][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:09:33.427][GoBackendProcess ][Error ] Process died
[10:09:33.689][IPCClient ][Info ] (34fc6747) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:33.689][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:33.999][IPCClient ][Info ] (44a2f3ae) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:33.999][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:34.307][IPCClient ][Info ] (e723a8d0) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:34.307][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:34.618][IPCClient ][Info ] (97c11103) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:34.618][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:34.927][IPCClient ][Info ] (ed27b726) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:34.927][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:35.239][IPCClient ][Info ] (e275a17d) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:35.239][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:35.548][IPCClient ][Info ] (f54837d6) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:35.548][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:35.856][IPCClient ][Info ] (7b3bb323) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:35.857][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:36.168][IPCClient ][Info ] (325423cf) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:36.169][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:36.479][IPCClient ][Info ] (e4c17c45) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:36.479][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:36.792][IPCClient ][Info ] (bcd84743) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:36.792][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:37.102][IPCClient ][Info ] (f3af63ac) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:37.102][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:37.417][IPCClient ][Info ] (39611072) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:37.417][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:37.730][IPCClient ][Info ] (3bd0a0bf) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:37.730][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:38.042][IPCClient ][Info ] (f36bdaf6) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:38.043][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:38.352][IPCClient ][Info ] (ddb1036b) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:38.352][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:38.430][GoBackendProcess ][Error ] Auto restarting process
[10:09:38.430][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:09:38.431][GoBackendProcess ][Info ] Started
[10:09:38.492][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:09:38.504][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:09:38.509][GoBackendProcess ][Error ] Process died
[10:09:38.663][IPCClient ][Info ] (76d9442d) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:38.663][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:38.974][IPCClient ][Info ] (b1ed1ccf) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:38.974][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:39.286][IPCClient ][Info ] (d3c60241) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:39.286][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:39.595][IPCClient ][Info ] (364cfa0c) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:39.595][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:39.907][IPCClient ][Info ] (019d4496) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:39.907][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:40.219][IPCClient ][Info ] (89636574) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:40.219][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:40.531][IPCClient ][Info ] (b33e3c83) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:40.531][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:40.840][IPCClient ][Info ] (e078e5ca) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:40.840][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:41.152][IPCClient ][Info ] (c690c1a1) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:41.152][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:41.465][IPCClient ][Info ] (7f23130c) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:41.465][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:41.777][IPCClient ][Info ] (116bb3a3) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:41.777][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:42.087][IPCClient ][Info ] (df9738e0) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:42.087][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:42.403][IPCClient ][Info ] (b5412331) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:42.403][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:42.715][IPCClient ][Info ] (59ede939) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:42.715][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:43.028][IPCClient ][Info ] (8a26d75a) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:43.028][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:43.341][IPCClient ][Info ] (3ace0408) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:43.341][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:43.511][GoBackendProcess ][Error ] Auto restarting process
[10:09:43.511][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:09:43.512][GoBackendProcess ][Info ] Started
[10:09:43.573][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:09:43.585][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:09:43.588][GoBackendProcess ][Error ] Process died
[10:09:43.652][IPCClient ][Info ] (5379a618) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:43.652][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:43.954][IPCClient ][Info ] (9bb12d71) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:43.954][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:44.264][IPCClient ][Info ] (885e6bcf) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:44.264][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:44.578][IPCClient ][Info ] (5d1ec07d) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:44.578][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:44.891][IPCClient ][Info ] (11c2cd4b) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:44.891][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:45.202][IPCClient ][Info ] (f20a9bbe) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:45.202][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:45.517][IPCClient ][Info ] (9a48b26c) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:45.517][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:45.829][IPCClient ][Info ] (11501a76) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:45.829][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:46.140][IPCClient ][Info ] (345c3083) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:46.140][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:46.452][IPCClient ][Info ] (835a9a64) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:46.452][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:46.767][IPCClient ][Info ] (6dd96701) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:46.767][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:47.076][IPCClient ][Info ] (322b3db1) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:47.076][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:47.378][IPCClient ][Info ] (a98439e6) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:47.378][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:47.680][IPCClient ][Info ] (bb9f6f42) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:47.680][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:47.990][IPCClient ][Info ] (426a3793) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:47.990][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:48.300][IPCClient ][Info ] (4fca7d12) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:48.300][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:48.596][GoBackendProcess ][Error ] Auto restarting process
[10:09:48.596][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:09:48.598][GoBackendProcess ][Info ] Started
[10:09:48.611][IPCClient ][Info ] (42a8ed7b) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:48.611][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:48.657][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:09:48.669][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:09:48.673][GoBackendProcess ][Error ] Process died
[10:09:48.921][IPCClient ][Info ] (8467f04e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:48.921][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:49.236][IPCClient ][Info ] (0cd67f21) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:49.236][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:49.547][IPCClient ][Info ] (12025983) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:49.547][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:49.852][IPCClient ][Info ] (f18d61e1) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:49.852][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:50.167][IPCClient ][Info ] (b4dc760f) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:50.167][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:50.474][IPCClient ][Info ] (599f8774) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:50.474][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:50.785][IPCClient ][Info ] (9615692a) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:50.785][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:51.100][IPCClient ][Info ] (cab50f5e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:51.100][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:51.411][IPCClient ][Info ] (aa12124c) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:51.411][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:51.724][IPCClient ][Info ] (93c88cd5) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:51.724][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:52.034][IPCClient ][Info ] (2a50873f) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:52.034][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:52.337][IPCClient ][Info ] (14e077a8) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:52.337][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:52.651][IPCClient ][Info ] (eb48beaa) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:52.651][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:52.965][IPCClient ][Info ] (77b18c11) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:52.965][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:53.279][IPCClient ][Info ] (4e2c0bcd) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:53.279][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:53.588][IPCClient ][Info ] (57bfbdd8) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:53.588][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:53.682][GoBackendProcess ][Error ] Auto restarting process
[10:09:53.682][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:09:53.684][GoBackendProcess ][Info ] Started
[10:09:53.760][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:09:53.772][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:09:53.776][GoBackendProcess ][Error ] Process died
[10:09:53.900][IPCClient ][Info ] (8b14137a) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:53.900][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:54.212][IPCClient ][Info ] (ed3cfb4a) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:54.212][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:54.522][IPCClient ][Info ] (08fa39ac) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:54.522][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:54.837][IPCClient ][Info ] (d6c99f8b) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:54.837][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:55.149][IPCClient ][Info ] (1e5d8caa) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:55.149][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:55.459][IPCClient ][Info ] (8b989ec8) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:55.459][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:55.769][IPCClient ][Info ] (9a7c5877) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:55.769][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:56.080][IPCClient ][Info ] (1cea9b0d) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:56.080][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:56.386][IPCClient ][Info ] (c547fe27) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:56.386][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:56.700][IPCClient ][Info ] (16789f95) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:56.700][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:57.011][IPCClient ][Info ] (c6213326) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:57.011][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:57.325][IPCClient ][Info ] (4a7c8865) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:57.326][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:57.636][IPCClient ][Info ] (f7f4bad5) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:57.636][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:57.950][IPCClient ][Info ] (5bd71b63) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:57.950][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:58.260][IPCClient ][Info ] (5e792af3) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:58.261][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:58.573][IPCClient ][Info ] (acc44c4c) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:58.573][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:58.791][GoBackendProcess ][Error ] Auto restarting process
[10:09:58.791][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:09:58.793][GoBackendProcess ][Info ] Started
[10:09:58.852][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:09:58.862][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:09:58.866][GoBackendProcess ][Error ] Process died
[10:09:58.883][IPCClient ][Info ] (85214931) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:58.883][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:59.193][IPCClient ][Info ] (ddd82fb4) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:59.193][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:59.504][IPCClient ][Info ] (d4fefd39) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:59.504][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:09:59.811][IPCClient ][Info ] (6a0629fe) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:09:59.811][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:10:00.122][IPCClient ][Info ] (b24187be) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:10:00.122][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:10:00.436][IPCClient ][Info ] (5d91122e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:10:00.437][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:10:00.743][IPCClient ][Info ] (2b0cd2aa) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:10:00.743][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:10:01.048][IPCClient ][Info ] (80967121) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:10:01.049][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:10:01.355][IPCClient ][Info ] (d2fdc4a9) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:10:01.355][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:10:01.660][IPCClient ][Info ] (1f03fafb) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:10:01.660][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:10:01.971][IPCClient ][Info ] (49540b0b) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:10:01.971][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:10:02.285][IPCClient ][Info ] (60e02d90) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:10:02.285][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:10:02.285][SettingsLoader ][Warning] Failed to fetch settings from backend, retrying in 1 sec
[10:10:02.285][IPCClient ][Info ] (ea6f4307) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:10:02.286][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:10:02.595][IPCClient ][Info ] (d3c4f353) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:10:02.595][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:10:02.906][IPCClient ][Info ] (ca0815d0) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:10:02.906][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:10:03.213][IPCClient ][Info ] (aa6cb045) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:10:03.213][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:10:03.521][IPCClient ][Info ] (9ec6d24e) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:10:03.521][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:10:03.832][IPCClient ][Info ] (3db0b640) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:10:03.832][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:10:03.878][GoBackendProcess ][Error ] Auto restarting process
[10:10:03.878][GoBackendProcess ][Info ] Starting C:Program FilesDockerDockerresourcescom.docker.backend.exe -addr unix:\.pipedockerBackendApiServer -native-api
[10:10:03.879][GoBackendProcess ][Info ] Started
[10:10:03.939][GoBackendProcess ][Error ] msg="unable to parse C:\Users\longq\AppData\Roaming\Docker\settings.json: open C:\Users\longq\AppData\Roaming\Docker\settings.json: The system cannot find the file specified."
[10:10:03.954][GoBackendProcess ][Fatal ] msg="reading C:\Users\longq\AppData\Roaming\Docker\locked-directories: while parsing JSON from C:\Users\longq\AppData\Roaming\Docker\locked-directories: invalid character '\x00' looking for beginning of value"
[10:10:03.958][GoBackendProcess ][Error ] Process died
[10:10:04.138][IPCClient ][Info ] (3fa15f28) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:10:04.138][GoBackendClient ][Warning] HttpOS Client: connection timed out.
[10:10:04.446][IPCClient ][Info ] (ccf4c519) 88292ab5-GoBackendClient-CSharp C->S GET /ping
[10:10:04.446][GoBackendClient ][Warning] HttpOS Client: connection timed out.
Thanks & Best regards,
Introduction
This article is focusing on how to solve an error message appear. It appear upon executing Docker Desktop in Microsoft Windows. The following is the appearance of the Docker Desktop error message :
Docker failed to initialize Docker Desktop is shutting down
In the above image, actually it exist in another article from the stackoverflow. It exist in this link where the main subject is ‘Docker Failed to Initialize on Windows’.The following is the image containing the error message :
Actually, the appearance is not too similar with the above display. Although the message in the error message dialog box is the same. The error message is ‘
Docker failed to initialize Docker Desktop is shutting down
‘. It depends on the version of the Docker Desktop. In this case, it is using Docker Desktop 4.2.
Solution
So, the following is the actual link to the solution of this problem. It is an article in one of the stackoverflow page in this link. There are several advices on solving the problem :
-
Restart the Windows operating system.
-
Uninstall the current Docker Desktop and reinstall it once more.
-
Delete all of the content exist in the following folders :
- C:UsersAdministratorAppDataLocalDocker
- C:UsersAdministratorAppDataRoamingDocker
- C:UsersAdministratorAppDataRoamingDocker Desktop
The above path is in ‘C:UsersAdministrator’ because Docker Desktop installation is using Admnistrator user account. Just change the path using the suitable user path accordingly.
-
After successfully delete all the contents in that folder, apparently, the following image of window display of Docker Desktop User Agreement appear :
Just check the checkbox with the label of ‘I accept the terms’. After that, the button with the label of ‘Accept’ will be visible. Just click that visible button to go further to accept ‘Service Agreement’.
-
Finally, after proceeding the above steps, the Docker Desktop fortunately is running normally.
Q
Why am I getting this «Docker failed to initialize» error?
A
After installing the latest version of Docker Desktop on Windows,
you can run «Docker Desktop» and hope it will work automatically.
But because of compatibility issues, running the latest version of Docker Desktop
on Windows with default options may give you the «Docker failed to initialize» error.
There are a number of reports of this error on the Internet.
Suggestions solutions include:
1. Un-install and re-install Docker Desktop on Windows.
It may or may not solve the problem.
2. Re-install an older version like 3.3.3.
It may or may not solve the problem.
3. Cleanup Docker personal settings directories.
It may or may not solve the problem.
> Del C:Users[USER]AppDataLocalDocker > Del C:Users[USER]AppDataRoamingDocker > Del C:Users[USER]AppDataRoamingDocker Desktop
If you terminate the Docker.Service from Task Manager,
and start Docker Desktop again, you may see more errors and
dead Docker consol screen.
If you look at the log file, you may see error messages like:
[GoBackendProcess ][Info ] msg="NewSharer: WSL2 engine is enabled so no file sharer is required." [GoBackendProcess ][Info ] msg="ipc.NewClient: e270741f-PathControllerPKG -> \\.\pipe\dockerBackendApiServer ... [GoBackendProcess ][Info ] msg="enabling filesystem caching" [GoBackendProcess ][Info ] msg="filesystem exports are: (2)" [GoBackendProcess ][Info ] msg="volume control server listening on \\.\pipe\dockerVolume" [GoBackendProcess ][Fatal ] msg="unable to start fileserver: unable to listen on 4099: A socket operation encountered a dead network." [GoBackendProcess ][Error ] Process died
So the best option is to try different old versions of Docker Desktop,
until you find one that works for your Windows system.
⇒ Install Docker Desktop 2.5.0 on Windows 10
⇐ Install Docker Desktop on Windows 10
⇑ Install Docker Desktop on Windows
⇑⇑ Docker Container Platform — Tutorials
Docker Desktop
Docker Desktop integrates with your preferred development tools and languages, as well as provides access to Docker Hub’s extensive library of verified images and templates. This allows development teams to extend their environment by leveraging a secure repository to quickly auto-build, continually integrate, and interact.
Docker Failed To Initialize
Docker is also known as Docker Platform, which is an open platform for creating, shipping, and executing applications. Docker desktop’s purpose is to provide a simple development environment for creating, distributing, and operating dockerized programmes. This is a means to implement the Twelve Factor App guideline’s Environment Parity and close the resource gap between development and production environments. As a result, a containerized application may be operated in your environment in the same way it is in production.
Docker Failed To Initialize Docker Desktop Is Shutting Down
If you fall into this issue, save yourself some time and rerun the installation:
-
Docker should be removed from the «Add or remove programmes» list.
-
Start your computer again.
-
Install Docker with administrative privileges (and not by running the installer directly)
If the installer prompts you to reboot, go ahead and do so. Docker Desktop for Windows should now launch and operate your containers as planned.
Docker Failed To Initialize Docker Desktop Is Shutting Down Windows 10
If you’re having trouble running Docker on your Windows 10 machine, try the troubleshooting steps below.
-
Start Docker Services
-
Turn on Hyper-V and Containers.
-
In Windows search, type Windows Feature and then click Turn Windows features on or off.
-
Select Containers and Hyper-V as shown below, then click OK.
-
Check Task Manager to see if Virtualization is enabled.
Disclaimer: The above information is for general informational purposes only. All information on the Site is provided in good faith, however we make no representation or warranty of any kind, express or implied, regarding the accuracy, adequacy, validity, reliability, availability or completeness of any information on the Site.
Docker Failed To Initialize Docker Desktop Is Shutting Down — FAQs
1. Why do we need Docker Desktop?
Docker Desktop is an easy-to-install application for your Mac or Windows environment that enables you to build and share containerized applications and microservices.
2. What is the main purpose of Docker?
It enables developers to package applications into containers.
3. Is Docker useful for Desktop applications?
Yes, Docker could help solve some challenges associated with desktop apps.
4. Is Docker desktop safe?
Docker containers are, by default, quite secure; especially if you run your processes as non-privileged users inside the container.
5. Why is Docker so popular?
Docker allows you to break down your application into smaller services.
6. What Docker means?
Docker is an open source software platform to create, deploy and manage virtualized application containers on a common operating system
7. Who created Docker?
Docker was created by Solomon Hykes.
Docker failed to initialize docker desktop is shutting down
This is one of the headbanging issues when docker stops working with the error as per image -1
Solution:
Go to
C:Users{username}AppDataLocalDocker
C:Users{username}AppDataRoamingDocker
C:Users{username}AppDataRoamingDocker 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.
Durga Charan Ojhahttps://lifeonnetwork.com/
I am a proud Indian, proud father, a blogger,
Being in a profession as System administrator, my passion is troubleshooting computer issues, I do like sharing solutions through blogging making videos of solving issues.
Содержание
- Cannot start Docker for Windows: Fails to Initialize #601
- Comments
- mitchellmaler commented Mar 22, 2017
- Expected behavior
- Actual behavior
- Information
- Steps to reproduce the behavior
- friism commented Apr 11, 2017
- valorisdev commented Apr 13, 2017
- nvn6w commented Apr 17, 2017 •
- mitchellmaler commented May 17, 2017 •
- shell client error
- Desktop Client Error:
- friism commented May 17, 2017
- mitchellmaler commented May 17, 2017
- valorisdev commented May 22, 2017 •
- Docker Failed to Initialize on Windows
- 7 Answers 7
- Docker failed to initialize #3088
- Comments
- Lemraj commented Dec 12, 2018 •
- Expected behavior
- Actual behavior
- Information
- Steps to reproduce the behavior
- Lemraj commented Jan 2, 2019
- tocklime commented Jan 28, 2019
- tocklime commented Jan 28, 2019
- Lemraj commented Jan 29, 2019
- kurdi89 commented Mar 28, 2019
- Sadiq-Rashid commented Apr 3, 2019
- wulfsolter commented Apr 3, 2019
- docker-desktop-robot commented Jul 3, 2020
- Docker failed to initialize #8618
- Comments
- PabloLigeroJDS commented Sep 22, 2020 •
- Expected behavior
- Actual behavior
- Information
- Log File:
- Steps to reproduce the behavior
- Docker Failed to Initialize #907
- Comments
- JamesCohen-awin commented Jul 10, 2017 •
- Expected behavior
- Actual behavior
- Information
- Steps to reproduce the behavior
- jasonbivins commented Jul 10, 2017
- DaleCulpin commented Jul 13, 2017 •
- DaleCulpin commented Jul 13, 2017 •
- docker-desktop-robot commented Mar 27, 2018
Cannot start Docker for Windows: Fails to Initialize #601
Expected behavior
Docker for win to start.
Actual behavior
Docker failed to initilize.
Information
Unable to create an instance of Docker.Actions: Unable to create an instance of Docker.WPF.WelcomeWindow
at Docker.Core.di.Singletons.NewInstance(Type type, Int32 depth)
at Docker.Core.di.Singletons.Get(Type type, Int32 depth)
at Docker.Core.di.Singletons.GetT
at Docker.Program.Run(IReadOnlyCollection`1 args)
Version: 17.03.0-ce-win1 (10296)
Channel: stable
Sha1: e5a07a1a69a5123c71e24ca2aa9e6f875fa26d08
Started on: 2017/03/22 09:36:29.985
Resources: C:Program FilesDockerDockerResources
OS: Windows 10 Enterprise
Edition: Enterprise
Id: 1607
Build: 14393
BuildLabName: 14393.693.amd64fre.rs1_release.161220-1747
File: C:UsersMM025313AppDataLocalDockerlog.txt
CommandLine: «C:Program FilesDockerDockerDocker for Windows.exe»
You can send feedback, including this log file, at https://github.com/docker/for-win/issues
[09:36:30.099][GUI ][Info ] Starting.
[09:36:30.417][Tracking ][Info ] Crash report and usage statistics are enabled
[09:36:30.421][SegmentApi ][Info ] Usage statistic: appLaunched
[09:36:30.538][NamedPipeClient][Info ] Sending Version().
[09:36:30.541][NamedPipeClient][Info ] Received response for Version
[09:36:30.541][SegmentApi ][Info ] Usage statistic: heartbeat
[09:36:30.540][NamedPipeServer][Info ] Version done in 00:00:00.
[09:36:30.820][GUI ][Error ] Unable to create an instance of Docker.Actions: Unable to create an instance of Docker.WPF.WelcomeWindow
[09:38:22.990][ErrorReportWindow][Info ] Open logs
Steps to reproduce the behavior
Try to start the Docker for Windows program/service. I immediately get the error and it wont start.
The text was updated successfully, but these errors were encountered:
Docker for Windows won’t run purely as a service. Are you trying to open the desktop app, or doing something else?
I’ve the same issue too.
I try to open the desktop app.
Unable to create an instance of Docker.Actions: Unable to create an instance of Docker.WPF.WelcomeWindow
à Docker.Core.di.Singletons.NewInstance(Type type, Int32 depth)
à Docker.Core.di.Singletons.Get(Type type, Int32 depth)
à Docker.Core.di.Singletons.GetT
à Docker.Program.Run(IReadOnlyCollection`1 args)
Crash report
log.txt
I have same problem.
I installed Docker Toolbox, Docker worked property. But when I started Kitematic, Windows has crashed. I reboot my PC and could not start Docker again.
Unable to create an instance of Docker.Actions: Unable to create an instance of Docker.WPF.WelcomeWindow
at Docker.Core.di.Singletons.NewInstance(Type type, Int32 depth)
at Docker.Core.di.Singletons.Get(Type type, Int32 depth)
at Docker.Core.di.Singletons.GetT
at Docker.Program.Run(IReadOnlyCollection`1 args)
Crash Report
log.txt
I just ran the installer again and I can see com.docker.service is running in the background. I tried to run powershell (Admin) and run docker commands and I get
shell client error
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.27/containers/json?all=1: 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.
When I click the desktop icon either normally or as admin for Docker for Windows I get presented with a error page that says:
Desktop Client Error:
Unable to create an instance of Docker.Actions: Unable to create an instance of Docker.WPF.WelcomeWindow
at Docker.Core.di.Singletons.NewInstance(Type type, Int32 depth)
at Docker.Core.di.Singletons.Get(Type type, Int32 depth)
at Docker.Core.di.Singletons.GetT
at Docker.Program.Run(IReadOnlyCollection`1 args)
I check the logs and here is what It says:
Version: 17.03.1-ce-win12 (12058)
Channel: stable
Sha1: d1db12684b33b778cfc3012e92959e50eb486fcd
Started on: 2017/05/17 08:24:39.162
Resources: C:Program FilesDockerDockerResources
OS: Windows 10 Enterprise
Edition: Enterprise
Id: 1607
Build: 14393
BuildLabName: 14393.1198.amd64fre.rs1_release_sec.170427-1353
File: C:UsersMM025313AppDataLocalDockerlog.txt
CommandLine: «C:Program FilesDockerDockerDocker for Windows.exe»
You can send feedback, including this log file, at https://github.com/docker/for-win/issues
[08:24:39.283][GUI ][Info ] Starting.
[08:24:39.613][Tracking ][Info ] Crash report and usage statistics are enabled
[08:24:39.617][SegmentApi ][Info ] Usage statistic: appLaunched
[08:24:39.731][NamedPipeClient][Info ] Sending Version().
[08:24:39.734][NamedPipeClient][Info ] Received response for Version
[08:24:39.734][SegmentApi ][Info ] Usage statistic: heartbeat
[08:24:39.733][NamedPipeServer][Info ] Version done in 00:00:00.
[08:24:40.010][GUI ][Error ] Unable to create an instance of Docker.Actions: Unable to create an instance of Docker.WPF.WelcomeWindow
[08:24:46.510][ErrorReportWindow][Info ] Open logs
Can you try the latest 17.05 edge installer?
It would also be good to have more details on your environment, eg. whether you’re running Docker for Windows in a VM or such.
I installed Version: 17.05.0-ce-win11 (12053) and I am still getting the same error when it starts up.
Version: 17.05.0-ce-win11 (12053)
Channel: edge
Sha1: ffbc5f5871f44611dfb2bbf49e8312332531c112
Started on: 2017/05/17 10:17:45.746
Resources: C:Program FilesDockerDockerResources
OS: Windows 10 Enterprise
Edition: Enterprise
Id: 1607
Build: 14393
BuildLabName: 14393.1198.amd64fre.rs1_release_sec.170427-1353
File: C:UsersMM025313AppDataLocalDockerlog.txt
CommandLine: «C:Program FilesDockerDockerDocker for Windows.exe»
You can send feedback, including this log file, at https://github.com/docker/for-win/issues
[10:17:45.859][GUI ][Info ] Starting.
[10:17:46.228][Tracking ][Info ] Crash report and usage statistics are enabled
[10:17:46.233][SegmentApi ][Info ] Usage statistic: appLaunched
[10:17:46.371][NamedPipeClient][Info ] Sending Version().
[10:17:46.375][NamedPipeClient][Info ] Received response for Version
[10:17:46.375][SegmentApi ][Info ] Usage statistic: heartbeat
[10:17:46.373][NamedPipeServer][Info ] Version done in 00:00:00.
[10:17:46.645][GUI ][Error ] Unable to create an instance of Docker.Actions: Unable to create an instance of Docker.WPF.WelcomeWindow
[10:17:46.657][CrashReport ][Info ] Preparing package to send with the diagnostics
[10:17:46.661][NamedPipeClient][Info ] Sending DownloadVpnKitLogs(C:UsersMM025313AppDataLocalTempvkgxrwpw.avwpcap.tar).
[10:17:46.661][NamedPipeClient][Info ] Sending DownloadVmLogs(C:UsersMM025313AppDataLocalTempvkgxrwpw.avwmobyLogs.tar).
[10:17:46.661][NamedPipeClient][Info ] Sending DownloadWinContainersDebugInfo(C:UsersMM025313AppDataLocalTempvkgxrwpw.avwwin_containers).
[10:17:46.662][NamedPipeClient][Info ] Sending GetDebugInfo().
[10:17:46.662][NamedPipeServer][Info ] DownloadVpnKitLogs(C:UsersMM025313AppDataLocalTempvkgxrwpw.avwpcap.tar)
[10:17:46.662][NamedPipeServer][Info ] DownloadWinContainersDebugInfo(C:UsersMM025313AppDataLocalTempvkgxrwpw.avwwin_containers)
[10:17:46.671][NamedPipeClient][Info ] Received response for DownloadVpnKitLogs
[10:17:46.663][VpnKit ][Warning] Unable to download logs: The operation has timed out.
[10:17:46.685][NamedPipeClient][Info ] Received response for DownloadVmLogs
[10:17:46.663][NamedPipeServer][Info ] DownloadVpnKitLogs done in 00:00:00.0009998.
[10:17:46.664][NamedPipeServer][Info ] DownloadVmLogs(C:UsersMM025313AppDataLocalTempvkgxrwpw.avwmobyLogs.tar)
[10:17:46.664][PowerShell ][Info ] Run script ‘(Get-VM MobyLinuxVM).Id.Guid’.
[10:17:46.669][NamedPipeServer][Info ] GetDebugInfo()
[10:17:46.685][HyperV ][Warning] Unable to download logs: Unrecognized Guid format.
[10:17:46.685][NamedPipeServer][Info ] DownloadVmLogs done in 00:00:00.0210094.
[10:17:48.208][ErrorReportWindow][Info ] Open logs
[10:17:57.675][NamedPipeClient][Info ] Received response for DownloadWinContainersDebugInfo
[10:17:57.675][NamedPipeServer][Info ] DownloadWinContainersDebugInfo done in 00:00:11.0131989.
[10:18:16.489][NamedPipeServer][Info ] GetDebugInfo done in 00:00:29.8203262.
[10:18:16.497][NamedPipeClient][Info ] Received response for GetDebugInfo
[10:18:17.352][CrashReport ][Info ] Uploading diagnostics.
[10:18:18.664][CrashReport ][Info ] Diagnostics successfully uploaded (8B19227C-B3B8-48C8-898A-F7C45E6F228E/2017-05-17_10-17-46)
[10:18:18.676][GUI ][Info ] Sending Bugsnag report 71b1f766-9edf-404c-beba-fc835e34e7ad.
[10:18:19.642][GUI ][Info ] Bugsnag report 71b1f766-9edf-404c-beba-fc835e34e7ad sent
My host OS is Windows 10 Enterprise and I am trying to run docker on that so no virtual machine. I made sure Hyper-V is enabled in the features.
Windows version: 1607
OS Build: 14393.1198
Dell Precision 5510
Processor: i7-6820HQ CPU @ 2.70GHz
RAM: 32GB.
The installer doesn’t fail but when I run Docker for Windows I am getting that error. I can run the CLI in powershell but it cannot connect to the daemon since it wont start up.
I have exactly the same problem
Shell client error
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.29/containers/json?all=1: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevted to connect. This error may also indicate that the docker daemon is not running.
Config
Источник
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.
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
7 Answers 7
Got the same issue and fixed it by deleting %appdata%Docker as mentioned by Github User «tocklime»
My solution: delete %appdata%Dockersettings.json and let Docker to create a new one.
Take a backup of the file for the next time it gets broken.
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.
Источник
Docker failed to initialize #3088
Expected behavior
Actual behavior
Information
Steps to reproduce the behavior
BTW: I have the same problem when installing the Edge version. Exactly the same error!
The text was updated successfully, but these errors were encountered:
Any progress on this issue?
I have a very similar issue, although my null reference is on line 190 (maybe just different version of the code). I did have hyper-v installed, and got this, and was just in the process of reinstalling hyper-v, and tried launching docker whilst hyper-v is not installed. I get the same error with and without hyper-v installed, so it must be pretty early on in the start up.
My diagnostics ID is AB547C5F-6008-421C-B78B-F10A6277FA58/20190128103346
I fixed whatever this was by deleting %appdata%Docker. I guess it had got screwed up somehow.
@tocklime Thanks a lot! Deleting the appdata folder fixed the problem!
thnx @tocklime, deleting the files in C:UsersxxxxxxxAppDataRoamingDocker did it
thanks,deleting the files in C:UsersxxxxxxxAppDataRoamingDocker fixed it
@kurdi89 & @cockers : Clicking the thumbs up 👍 button below a comment is enough to let the author know they’ve helped you. Otherwise many people get notifications just to see that you’ve also done what someone else told you to do. Thank you! 🙏
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
You can’t perform that action at this time.
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.
Источник
Docker failed to initialize #8618
Expected behavior
Run Dockers for desktop. I expected the aplication to open, but an Error window of Docke appears.
Actual behavior
An Error window appear with information about the error. In the logs ( attached below ) it can be appreciated that is a problem related with the configuration. but Im not sure.
Information
Log File:
Version: 2.3.0.5 (48029)
Channel: stable
Sha1: c2bacb43a7aec4c9d7ed0bdc73106464c0861e18
Started on: 2020/09/22 09:55:07.013
Resources: C:Program FilesDockerDockerresources
OS: Windows 10 Enterprise
Edition: Enterprise
Id: 1803
Build: 17134
BuildLabName: 17134.1.amd64fre.rs4_release.180410-1804
File: C:UsersxxxxxxxxAppDataLocalDockerlog.txt
CommandLine: «C:Program FilesDockerDockerDocker Desktop.exe»
You can send feedback, including this log file, at https://github.com/docker/for-win/issues
[09:55:07.097][GUI ][Info ] Starting.
[09:55:07.113][ComponentVersions ][Info ] Edition community
[09:55:07.113][ComponentVersions ][Info ] Edition community
[09:55:07.298][AppMigrator ][Info ] Current version: 6. Latest version: 6
[09:55:07.314][TrackingSettings ][Info ] Crash report and usage statistics are enabled
[09:55:07.314][SegmentApi ][Info ] Usage statistic: Identify
[09:55:07.403][SegmentApi ][Warning] Failed to Identify: Configuration system failed to initialize
[09:55:07.405][SegmentApi ][Info ] Usage statistic: appLaunched
[09:55:07.410][SegmentApi ][Warning] Failed to track event appLaunched: Configuration system failed to initialize
[09:55:07.412][ApplicationTemplatesTracking][Info ] Docker template not found, skipping analytics.
[09:55:07.412][SegmentApi ][Info ] Usage statistic: heartbeat
[09:55:07.412][SegmentApi ][Warning] Failed to track event heartbeat: Configuration system failed to initialize
[09:55:07.412][GUI ][Error ] System.ArgumentException:
Unable to create an instance of Docker.App: Unable to create an instance of Docker.WPF.Nps.NPS: Unable to create an instance of Docker.WPF.Nps.WootricService: Exception has been thrown by the target of an invocation.
at Docker.Core.Di.Singletons.NewInstance(Type type, Int32 depth) in C:workspacesstable-2.3.xsrcgithub.comdockerpinatawinsrcDocker.CorediSingletons.cs:line 89
at Docker.Core.Di.Singletons.Get(Type type, Int32 depth) in C:workspacesstable-2.3.xsrcgithub.comdockerpinatawinsrcDocker.CorediSingletons.cs:line 51
at Docker.Core.Di.Singletons.GetT in C:workspacesstable-2.3.xsrcgithub.comdockerpinatawinsrcDocker.CorediSingletons.cs:line 28
at Docker.Program.Run(IReadOnlyCollection`1 args) in C:workspacesstable-2.3.xsrcgithub.comdockerpinatawinsrcDocker.DesktopProgram.cs:line 320
System.ArgumentException:
Unable to create an instance of Docker.WPF.Nps.NPS: Unable to create an instance of Docker.WPF.Nps.WootricService: Exception has been thrown by the target of an invocation.
at Docker.Core.Di.Singletons.NewInstance(Type type, Int32 depth) in C:workspacesstable-2.3.xsrcgithub.comdockerpinatawinsrcDocker.CorediSingletons.cs:line 89
at Docker.Core.Di.Singletons.Get(Type type, Int32 depth) in C:workspacesstable-2.3.xsrcgithub.comdockerpinatawinsrcDocker.CorediSingletons.cs:line 51
at System.Linq.Enumerable.WhereSelectArrayIterator 2.MoveNext() at System.Linq.Buffer 1..ctor(IEnumerable 1 source) at System.Linq.Enumerable.ToArray[TSource](IEnumerable 1 source)
at Docker.Core.Di.Singletons.NewInstance(Type type, Int32 depth) in C:workspacesstable-2.3.xsrcgithub.comdockerpinatawinsrcDocker.CorediSingletons.cs:line 83
[09:55:07.427][GUI ][Info ] Sending Bugsnag report bfef7bac-2967-4be5-833e-57b03d1828fe.
[09:55:07.514][GUI ][Info ] Bugsnag report bfef7bac-2967-4be5-833e-57b03d1828fe sent
[09:55:07.514][SegmentApi ][Info ] Usage statistic: eventCrash
[09:55:07.514][SegmentApi ][Warning] Failed to track event eventCrash: Configuration system failed to initialize
[09:55:07.514][Diagnostics ][Warning] Starting to gather diagnostics as User : ‘C:Program FilesDockerDockerresourcescom.docker.diagnose.exe’ gather.
[09:55:35.303][ErrorReportWindow ][Info ] Open logs
[10:13:41.507][Diagnostics ][Info ] Uploading diagnostics 09308469-E60C-4778-A18E-152CAC0B625D/20200922075507
[10:13:42.780][Diagnostics ][Info ] Uploaded succesfully diagnostics 09308469-E60C-4778-A18E-152CAC0B625D/20200922075507
[10:24:56.719][ErrorReportWindow ][Info ] Open logs
I tried to install several times docker but I was never able to lunch it. Is the first time I install and use Dockers for windows.
Steps to reproduce the behavior
Install Dockers Desktop and lunch the program.
The text was updated successfully, but these errors were encountered:
Источник
Docker Failed to Initialize #907
Expected behavior
Docker Engine would start
Actual behavior
Received an error message «Docker Failed to Initialize»
Information
Crash report id: 1431A2DE-2CC1-4A2D-B291-C723A6BD1056/2017-07-10_10-27-23
Steps to reproduce the behavior
Turn on machine. Wait for it to launch Docker via the startup.
The text was updated successfully, but these errors were encountered:
I’m getting this same issue.
Occasionally it will start up fine, but mostly it fails with this ‘Docker Failed to Initialize’ message, then a subsequent Windows 10 generic application error message.
I’ll try running the linked diagnostics script above when I get home tonight and post results.
Here is my Docker debug script output in Powershell;
I enabled Windows 10 Containers to fix the first issue I found but the rest of this I’m not sure how to resolve. The script’s README is still be be completed for the sections related to these errors.
Seems to be hinting at a NAT issue.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.
Prevent issues from auto-closing with an /lifecycle frozen comment.
If this issue is safe to close now please do so.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale
Источник