I am trying to install the Docker community edition for windows, the installation was successful and it asked me to logout and login again and I did same. But when I tried to start the docker it says —
A task was canceled.
at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters)
at Docker.WPF.BackendClient.Version()
at Docker.Program.Run(IReadOnlyCollection`1 args)
It is giving me below options —
Any help or pointers will really helpful.
asked Jul 6, 2017 at 6:22
1
Just need to delete the files in C:\Users\xxxxxxx\AppData\Roaming\Docker fixed it
answered Aug 18, 2021 at 9:59
Anil KumarAnil Kumar
1,5761 gold badge5 silver badges2 bronze badges
3
Deleting C:\Users\UserName\AppData\Roaming\Docker folder also resolved my issue.
buddemat
4,61214 gold badges29 silver badges50 bronze badges
answered Aug 24, 2021 at 9:10
Gokce DemirGokce Demir
4594 silver badges5 bronze badges
Just Remove all files under this paths:
C:\Users[USER]\AppData\Local\Docker
C:\Users[USER]\AppData\Roaming\Docker
C:\Users[USER]\AppData\Roaming\Docker Desktop
Once deleted, I didn’t have to do anything else, Docker Desktop started booting up as normal.
answered Sep 23, 2021 at 4:16
I did finally solve the problem and the solution was to restart the machine, which was not properly documented in the official site. As per the site —
Install
Double-click InstallDocker.msi to run the installer.
When the installation finishes, Docker starts automatically. The whale in the notification area indicates that Docker is running, and accessible from a terminal.
Run
Open a command-line terminal like PowerShell, and try out some Docker commands!
Run docker version to check the version.
Run docker run hello-world to verify that Docker can pull and run images.
However it needs a restart to enable virtualization, simply logging off and login again did not work for me as directed by the wizard. Most of the problems related to docker gets resolved by restarting the docker some of the common problems and the resolutions are as follows
- Docker not starting in windows or not working properly
- Change it to Linux containers
- Make sure that docker is installed on machine
- Make sure virtualization is enabled and docker starts successfully
answered Jul 6, 2017 at 6:53
JeetJeet
5,5698 gold badges44 silver badges75 bronze badges
1
Proxy was the culprit in my case:
In the log file in %LOCALAPPDATA%\Docker,
[11:43:09.152][GoBackendProcess ][Error ] msg=“while parsing JSON from C:\Users[USER]\AppData\Roaming\Docker\settings.json: json: cannot unmarshal bool into Go struct field Content.proxyHttpMode of type string”
Open %APPDATA%\Docker\settings.json
I removed all settings lines related to proxy, and the service started fine.
Alternatively, you can delete the following directories:
%LOCALAPPDATA%\Docker
%APPDATA%\Docker
%APPDATA%\Docker Desktop
answered Aug 18, 2021 at 5:30
Jayesh MannJayesh Mann
3062 silver badges5 bronze badges
I had a similar issues generated by the following error described in the C:\Users\<myuser>\AppData\Local\Docker\log.txt:
[12:35:12.988][GUI ][Warning] Failed to configure docker scan: System.UnauthorizedAccessException: O acesso ao caminho 'C:\Users\<myuser>\.docker\scan\config.json' foi negado.
em System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
To solve that I just dropped the folder located at C:\Users\<myuser>\.docker and run the Docker Desktop again.
answered Feb 19, 2022 at 15:44
**
Just Delete the files in C:\Users\xxxxxxx\AppData\Roaming\Docker fixed
itIt helps me !!!
**
answered Oct 20, 2021 at 7:08
Suraj VermaSuraj Verma
4636 silver badges8 bronze badges
i didn’t find correct solutions here, even though it’s the first page of google, just do the following:
- Go to C:\Users%user%\AppData\Roaming\Docker
- Delete file locked-directories
Profit!
Hope this helps a lot.
answered Dec 1, 2022 at 10:27
1
I just uninstalled/installed docker and that solved all the issues
answered Apr 20 at 1:36
CarlosCarlos
3,6601 gold badge17 silver badges14 bronze badges
- 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 Files\Docker\Docker\resources
OS: Windows 10 Home
Edition: Core
Id: 2009
Build: 19042
BuildLabName: 19041.1.amd64fre.vb_release.191206-1406
File: C:\Users\longq\AppData\Local\Docker\log.txt
CommandLine: "C:\Program Files\Docker\Docker\Docker 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:\workspaces\PR-16070\src\github.com\docker\pinata\win\src\Docker.Core\cli\ScanOptionsLoader.cs:line 18
at Docker.Program.CheckDockerScanConfigFile(Logger logger) in C:\workspaces\PR-16070\src\github.com\docker\pinata\win\src\Docker.Desktop\Program.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:\workspaces\PR-16070\src\github.com\docker\pinata\win\src\Docker.Desktop\Program.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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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 Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\\.\pipe\dockerBackendApiServer -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,
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}\AppData\Local\Docker
C:\Users\{username}\AppData\Roaming\Docker
C:\Users\{username}\AppData\Roaming\Docker Desktop
I have made the username bold as it should be different for you as shared mine
Delete all those docker folders or rename them.
Then open Docker as run as administrator, It should create fresh folders and open smoothly without any error.
Or by any chance, it throws an error, try uninstalling the Docker and delete the folders from the Program Files folder too, as mentioned below. then download and install a specific version of docker required.
Get inside
C:\Program Files
C:\ProgramData
C:\Program Files (x86)
Delete those docker folders or rename them.
After following the above steps, You should be able to run docker smoothly.
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.
Table of content
- Introduction
- Reasons for Docker Desktop Failure
- Troubleshooting Steps
- Reinstalling Docker Desktop
- Conclusion
- Additional Resources (if applicable)
- Frequently Asked Questions (if applicable)
Introduction
When running Docker Desktop, encountering issues such as failure to initialize can be frustrating, especially when it results in shutting down the application. There are a number of reasons why this error might occur, from compatibility issues to inadequate hardware resources. However, understanding the causes and potential solutions can help prevent this from happening in the future.
In this article, we’ll explore some of the reasons Docker Desktop might fail to initialize and how you can troubleshoot and fix the problem. We’ll also provide some general tips for optimizing your system’s performance to ensure Docker Desktop runs smoothly. Whether you’re new to Docker or an experienced user, this guide can help you avoid frustration and get back to deploying containers quickly and efficiently. So let’s dive in and find out what you need to know.
Reasons for Docker Desktop Failure
There can be several reasons why Docker Desktop fails to initialize and shuts down on a system. Some of the common reasons include:
-
Resource Constraints: Docker Desktop requires a significant amount of resources to run effectively. If your system is low on resources such as memory or disk space, it can cause Docker to fail during initialization.
-
Conflicts with Other Applications: Docker Desktop might fail to initialize if there is any conflict with other applications installed on your system. For example, antivirus software might block Docker from accessing certain files, resulting in a failure.
-
Compatibility Issues: Docker Desktop might fail to initialize if your system is not compatible with the version of Docker you are using. For example, if you are using an outdated operating system or an incompatible version of Docker, it can result in failure.
-
Missing Dependencies: Docker Desktop might require specific dependencies to run effectively, such as container runtimes or virtualization drivers. If any such dependencies are missing or not installed correctly, it can cause Docker to fail during initialization.
It is essential to identify the underlying cause of Docker Desktop failure to take remedial action effectively. In the next section, we will cover some troubleshooting steps to fix the most common issues related to Docker Desktop.
Troubleshooting Steps
If you encounter the error message «Oh no! Docker Desktop failed to initialize and is shutting down,» here are some you can take:
-
Restart Docker Desktop: Sometimes, restarting the application can resolve the issue. Simply close the Docker Desktop application and open it again.
-
Check for updates: Make sure you are running the latest version of Docker Desktop. You can do this by clicking on the Docker icon in the taskbar and selecting «Check for Updates.» If an update is available, install it and see if the issue is resolved.
-
Restart your computer: A simple restart can often fix issues with software applications, so try restarting your computer and opening Docker Desktop again.
-
Check system requirements: Ensure that your computer meets the minimum system requirements for Docker Desktop. Check for things like free disk space, available RAM, and virtualization support. You can find the system requirements on the Docker website.
-
Uninstall and reinstall Docker Desktop: If none of the above steps work, you may need to uninstall and reinstall Docker Desktop. Make sure to backup any Docker containers or images you have before uninstalling.
These should help you resolve the issue and get Docker Desktop up and running again. If you continue to encounter problems, reach out to the Docker community or support team for additional help.
Reinstalling Docker Desktop
If you’ve encountered an issue with Docker Desktop failing to initialize and shutting down, reinstalling the software may be the solution. Here are the steps to reinstall Docker Desktop:
- Uninstall Docker Desktop:
- On Windows: Go to
Control Panel > Programs > Programs and Features. Select Docker Desktop from the list of installed software and click Uninstall. - On MacOS: Drag the Docker icon from the Applications folder to the Trash.
- Remove leftover files:
- On Windows: Delete the
C:\Program Files\Dockerand%USERPROFILE%\.dockerdirectories. - On MacOS: Open Terminal and enter the following commands to remove Docker files:
$ sudo rm -rf /Applications/Docker.app
$ sudo rm -rf /Users/$USER/Library/Application Support/Docker
$ sudo rm -rf /var/lib/docker
$ sudo rm -rf /var/run/docker.sock
- Reinstall Docker Desktop:
- Download the latest version of Docker Desktop from the official Docker website.
- Follow the installation instructions for your operating system.
Once the software is reinstalled, try running Docker Desktop again. Hopefully, the issue has been resolved and Docker Desktop will initialize properly. If the problem persists, it may be worth reaching out to Docker support for further assistance.
Conclusion
:
In , Docker Desktop is an essential tool for developers who want to create, test and deploy applications in various environments. When encountering issues with Docker Desktop, it’s important to remain calm and diagnose the problem using the tips and tools provided in this article. By understanding what went wrong, you can take steps to fix the issue and get back to coding without missing a beat.
Whether you’re a seasoned professional or a beginner in the world of software development, Docker Desktop can be a valuable tool in your arsenal. With its versatility and ease of use, it has become an indispensable tool for many developers and organizations around the world. And with the continued growth of technology, it is likely that Docker Desktop and other tools like it will only become more important in the years to come.
So if you experience any issues with Docker Desktop, don’t panic. Instead, take a deep breath, refer to this article for guidance, and resolve the issue step by step. With patience and perseverance, you can overcome any Docker Desktop hurdle and continue to develop your skills in the fast-paced world of software development.
Additional Resources (if applicable)
If you’re encountering issues with Docker Desktop failing to initialize, there are a few additional resources you can consult to troubleshoot the problem. Here are some helpful links:
-
Docker Desktop Troubleshooting
This official Docker documentation offers a comprehensive guide to resolving common issues with Docker Desktop. -
Docker Desktop Forums
The Docker Desktop forums are a great place to ask questions and seek help from the Docker community. -
GitHub Issues
If you believe you’ve encountered a bug or issue with Docker Desktop, you can file a report on the project’s GitHub page.
By consulting these resources and seeking assistance from the community, you can hopefully resolve the issue and get back to using Docker Desktop.
Frequently Asked Questions (if applicable)
Frequently Asked Questions
If you’re encountering issues with Docker Desktop failing to initialize and shutting down, you may be wondering what the problem is and what steps you can take to fix it. Here are some frequently asked questions that may help you:
What causes Docker Desktop to fail to initialize?
There are several potential causes for this problem, including:
- Incompatible hardware or operating system requirements
- Conflicts with other software or system settings
- Firewall or network issues
- Insufficient system resources, such as RAM or disk space
How can I troubleshoot Docker Desktop initialization issues?
If you’re having trouble getting Docker Desktop to start, here are a few things you can try:
- Check the system requirements to ensure that your hardware and operating system meet the minimum specifications for running Docker Desktop
- Disable any antivirus or firewall software temporarily to see if they are causing conflicts with Docker Desktop
- Check your network settings to ensure that Docker Desktop has the necessary permissions to access the internet
- Restart your computer and try launching Docker Desktop again to see if the issue resolves itself
What should I do if none of these solutions work?
If you’ve tried all of the troubleshooting steps and still can’t get Docker Desktop to initialize, you may want to consider seeking further assistance. The Docker community forums and support channels can be a great resource for finding solutions to technical issues. Alternatively, you may need to seek professional technical support or consult with a Docker expert to get your system up and running.
The Docker failed to initialize 2022 because your main document contains irrelevant data confusing your application and blocking the Docker desktop. On the flip side, we experienced an identical start Docker code exception when Docker failed to initialize wsl2 because the machine did not document the changes to the official site correctly.
To overcome this challenge, we researched the Docker container, located the failed inputs, and found the most sophisticated debugging approaches that will help you as well to overcome the Docker desktop failed to initialize Windows 10. In addition, we will exemplify why Docker failed using real-life scripts and syntaxes to help you troubleshoot the document and reenable the Docker download function.
Contents
- Why Is the Docker Failed to Initialize Error Happening?
- – Installing and Launching the Latest Docker Update
- – Disabling the Experimental Docker Features
- How To Fix the Docker That Failed to Initialize? Our Recommendations
- – Deleting the JSON Settings File
- Conclusion
Why Is the Docker Failed to Initialize Error Happening?
The Docker failed to initialize Docker desktop is shutting down Windows 11 error is happening because your primary document has irrelevant data and files. As a result, you cannot install Docker community editor for Windows. Although the installation was successful, most of your commands are not fully functional.
For instance, this code exception happens when the program introduces new files after installation, which should not occur with bug-free applications. As a result, Docker failed to initialize Docker desktop is shutting down, confirming the document’s inconsistencies and broken data.
Unfortunately, this is one of the many culprits for the Docker mistake because the bug can also happen due to incorrect locations of the JSON files. Although this rarely happens, it can confuse your program and force the code exception confirming Docker failed to initialize Docker desktop is already running.
On the flip side, this bug is sometimes challenging to pinpoint and fix because the installation does not indicate any issues or errors. In addition, the message box tells you to log out and log in after completing the installation, which is logical because the program must save the changes before running its properties.
As a result, we wrote several chapters to help you clear these inconsistencies and repair your document without affecting other operations and procedures. You will also learn how to scan your script for the Docker failed to initialize Docker desktop is shutting down Windows 10 code exception before applying the debugging methods.
– Installing and Launching the Latest Docker Update
We confirmed that this Docker bug will almost always happen when installing and launching the latest update because the program creates new files. Unfortunately, some systems face challenges recognizing the inputs and rendering the data, forcing your program to display the exception. As a result, we will exemplify the installation log providing more information on the new documents.
The following example provides the entire installation log:
Sha1: eb84a71876f14fe31a1i856896cb8b137e6e541763
Started on: 2022/11/30 08:34:58.342
Resources: C:\Program Files\Docker\Docker\resources
OS: Windows 11 Pro
Edition: Professional
Build: 12595
CommandLine: “C:\Program Files\Docker\InstallerCli.exe” -k -p
You can send feedback, including this log file, at https://github.com/docker/for-win/issues
[08:34:58.712][Installer ][Info ] Killing existing com.docker.service process with PID 6304
[08:34:59.502][Installer ][Info ] Preparing upgrade…
[08:34:59.695][HyperV ][Warning] Hyper-V is not installed on the machine
[08:35:00.120][LinuxWSL2Engine ][Info ] Debian: found credsStore with desktop.exe, rewriting
[08:35:00.190][Installer ][Info ] Prepare upgrade completed successfully
[08:35:00.190][Installer ][Info ] Fixing permissions…
[08:35:00.191][Installer ][Info ] Deleting directory C:\Program Files\Docker\cli-plugins
[08:35:00.192][Installer ][Info ] removing permission inheritance from C:\ProgramData\DockerDesktop
[08:35:00.193][Installer ][Info ] removing ACLs except for SYSTEM and Administrators from C:\ProgramData\DockerDesktop
[08:35:00.194][Installer ][Info ] removing permission inheritance from C:\Program Files\Docker\cli-plugins
[08:35:00.195][Installer ][Info ] removing ACLs except for SYSTEM and Administrators from C:\Program Files\Docker\cli-plugins
[08:35:00.196][Installer ][Info ] granting ReadAndExecute to everyone for C:\Program Files\Docker\cli-plugins
[08:35:00.198][Installer ][Info ] removing permission inheritance from C:\ProgramData\Docker
[08:35:00.200][Installer ][Info ] removing ACLs except for SYSTEM and Administrators from C:\ProgramData\Docker
[08:35:00.210][Installer ][Info ] granting ReadWriteDelete to authenticated users for C:\ProgramData\Docker\config
As you can tell, this exception is filled with flaws and inconsistencies, ruining your programming experience and halting further procedures. Still, this is one of the few culprits for this persistent bug.
– Disabling the Experimental Docker Features
Your application encounters this exception, although disabling the experimental Docker features confuses the system. In addition, we tried updating the latest Docker version to prevent the error, which was all in vain because the machine installed the files blocking your program from the former chapter. As a result, check the output of your Docker executable file to locate inconsistencies and flaws.
The following example provides the output:
[SKIP] DD0028: is there available VM disk space?
[FAIL] DD0031: does the Docker API work? error during connect: This error indicates that the docker daemon is not running.: Get “http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/v1.24/containers/json?limit=0”: open //./pipe/docker_engine_linux: The system cannot find the file specified.
[PASS] DD0016: is the LinuxKit VM running?
[FAIL] DD0001: is the application running? Docker is not running
[PASS] DD0017: can a VM be started?
[PASS] DD0024: is WSL installed?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? exit status 0xffffffff
[FAIL] DD0035: is the VM time synchronized? exit status 0xffffffff
[FAIL] DD0003: is the Docker CLI working? exit status 1
[PASS] DD0013: is the $PATH ok?
[FAIL] DD0007: is the backend responding? failed to ping com.docker.backend with error: Get “http://ipc/ping”: open \\.\pipe\dockerBackendApiServer: The system cannot find the file specified.
2022/07/19 15:49:06 exit status 0xffffffff
You must not avoid this critical troubleshooting step because you will learn more about the error’s cause. Hence, you can take action quickly and reenable your program.
How To Fix the Docker That Failed to Initialize? Our Recommendations
You can fix the docker that failed to initialize error by deleting the irrelevant Docker files that are confusing your program. The roaming data installed by the latest Docker upgrade will clear all inconsistencies. Alternatively, you can fix it by executing a specific command and starting the Docker services.
Although deleting the Docker files is the fastest debugging approach for this dynamic mistake, it is not the only one. Hence, we will teach you how to execute the program files command to initiate the debugging approach. Later, you must mess around with the Service Configuration Panel settings.
We suggest introducing the following command line:
C:\ Users\ Administrator > cd \
C:\ > cd “Program Files”
C:\ Program Files > cd Docker
C:\ Program Files\ Docker > cd Docker
C:\ Program Files\ Docker\ Docker > DockerCli.exe -SwitchDaemon
C:\ Program Files\ Docker\ Docker>
This brief procedure pinpoints and starts the debugging operation by providing the correct locations. As you can tell, you can find critical data about Docker in your Program Files. This data is vital when restarting the Docker services. However, the solution is only complete after making changes to the Service Configuration Panel.
Namely, navigate and stop the Docker service in the Service Configuration Panel. This ensures the program renders the changes made by the former code snippet. Then, you must restart the Docker service to launch the program and complete the solution. Luckily, this method does not mess up other functions and commands.
– Deleting the JSON Settings File
As formerly explained, you can get around this mistake by deleting the latest Docker files in your document. You can quickly locate the JSON settings file because it exists in the same Docker folder. Although the location is different for each system, you can typically find it in the User’s home and an additional Docker path. Alternatively, you can pinpoint the JSON settings file with a similar pattern.
However, after deleting the specific file, you must restart the system to complete and save the changes on your machine. This ensures the program renders all inputs without issues or mistakes. Lastly, you can run the Docker desktop application after restarting your computer and saving the changes. The error will disappear, and you can finally enjoy your programming experience.
Conclusion
The Docker failed to initialize because your main document contains irrelevant data confusing your application and blocking the desktop application. So, let us remember this article’s critical points in the following bullet list:
- The mistake can happen when the machine does not document the changes to the official site correctly
- The latest Docker update installs several incorrect files
- Deleting the irrelevant Docker files removes the exception and fixes your project
- The alternative debugging approach suggests messing around with the Service Configuration Panel settings
Experiencing this mistake after applying the debugging methods is unlikely, especially with simple applications. So, open your forgotten project, apply the solutions, and complete your application.
- Author
- Recent Posts
Your Go-To Resource for Learn & Build: CSS,JavaScript,HTML,PHP,C++ and MYSQL. Meet The Team