Docker allways says starting will not respond to command line

Docker Desktop
1

I have reinstalled and generated a log i do not understand?

[2026-06-05T21:01:43.970460000Z][com.docker.diagnose.exe.ipc] (279fbabe-6) 6220a573-DiagkitPKG C<-S bb8235c1-BackendAPI GET /network/tcp (1.1197ms): {}
[2026-06-05T21:01:43.971000000Z][com.docker.diagnose.exe.ipc] (279fbabe-7) 6220a573-DiagkitPKG C->S BackendAPI GET /idle
[2026-06-05T21:01:43.972074500Z][com.docker.diagnose.exe.ipc] (279fbabe-7) 6220a573-DiagkitPKG C<-S bb8235c1-BackendAPI GET /idle (1.0745ms): {"busyReason":["timed activities: map[/idle/make-busy:17603101500]"],"timedActivities":{"/idle/make-busy":17603101500},"vmRunning":true}
[2026-06-05T21:01:43.972692300Z][com.docker.diagnose.exe.ipc] (279fbabe-8) 6220a573-DiagkitPKG C->S BackendAPI GET /socketforwarder/debug
[2026-06-05T21:01:43.973231500Z][com.docker.diagnose.exe.ipc] (279fbabe-8) 6220a573-DiagkitPKG C<-S bb8235c1-BackendAPI GET /socketforwarder/debug (539.2µs): OK
[2026-06-05T21:01:43.973776600Z][com.docker.diagnose.exe.ipc] 10509e2d-DiagkitPKG -> \\.\pipe\dockerDebugSocketforwarder BackendAPI
[2026-06-05T21:01:43.973776600Z][com.docker.diagnose.exe.ipc] (aa2e2843-0) 10509e2d-DiagkitPKG C->S BackendAPI GET /socketforwarder/debug
[2026-06-05T21:01:48.974140400Z][com.docker.diagnose.exe.ipc][W] (aa2e2843-0) 10509e2d-DiagkitPKG C<-S ConnectionClosed GET /socketforwarder/debug (5.0003638s): Get "http://ipc/socketforwarder/debug": context deadline exceeded
[2026-06-05T21:01:48.974764600Z][com.docker.diagnose.exe.ipc] (279fbabe-9) 6220a573-DiagkitPKG C->S BackendAPI GET /mutagen/file-shares
[2026-06-05T21:01:48.976551300Z][com.docker.diagnose.exe.ipc][W] (279fbabe-9) 6220a573-DiagkitPKG C<-S bb8235c1-BackendAPI GET /mutagen/file-shares (1.7867ms): daemon not running
[2026-06-05T21:01:48.977112500Z][com.docker.diagnose.exe] Gathering BackendGatherer took 2m11.0151767s
[2026-06-05T21:02:01.575349500Z][com.docker.diagnose.exe.ipc] (69d8d986-6) 9cc0c636-diagnose C->S BackendAPI POST /idle/make-busy
[2026-06-05T21:02:01.576437600Z][com.docker.diagnose.exe.ipc] (69d8d986-6) 9cc0c636-diagnose C<-S bb8235c1-BackendAPI POST /idle/make-busy (1.0881ms): 0x35c306d506d8
[2026-06-05T21:02:24.503958800Z][com.docker.diagnose.exe] Gathering ProfileGatherer took 1m45.1974717s
[2026-06-05T21:02:24.503958800Z][com.docker.diagnose.exe] All 138 gatherers finished in 2m46.542023s

l
im a new user so i cant upload the log does this help?

2

I reformatted the code, because aligning it to the center made it really difficult to understand the logs. Please, use code blocks in MarkDown or click on the </> button when sharing code, terminal output, logs or anything with special characters.

Regarding the issue, I’m not sure I understand the topic title. Do you mean Docker actually says that it wil not respond to the command line or you mean it says “Docker daemon is starting” and at the same time you noticed that Docker does not respond when using the docker command in the command line?

What is your Docker Desktop version? Doy ou have a proxy or VPN enabled on the host?

These are just general questions, as “Docker daemon is not starting” is a common issue with no single solution and I still don’t know when that “socketforwarder” can fail..