Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get http://unix/engine/daemon.json: net/http: request canceled (Client.Timeout exceeded while awaiting headers) #5744

Closed
RobertNickRevnic opened this issue Feb 12, 2020 · 13 comments

Comments

@RobertNickRevnic
Copy link

RobertNickRevnic commented Feb 12, 2020

Hello! After I installed Docker Desktop and restarted the computer, it tried to start automatically. After a few minutes, the following errors occurred:

Docker.Core.Backend.BackendDestroyException: One or more errors occurred. at Docker.Core.Pipe.NamedPipeClient.<TrySendAsync>d__5.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters) at Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean withNotifications) at Docker.Actions.<>c__DisplayClass26_0.<StartAsync>b__0() at Docker.ApiServices.TaskQueuing.TaskQueue.<>c__DisplayClass18_0.<.ctor>b__1()

System.AggregateException: One or more errors occurred. at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken) at Docker.Backend.LifecycleClient.DockerStart() at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings, String daemonOptions, Credential credential) at Docker.Backend.ContainerEngine.Linux.Start(Settings settings, String daemonOptions, Credential credential)

 `Docker.Core.HttpBadResponseException:
 unable to fetch daemon.json: Get http://unix/engine/daemon.json: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
    at Docker.Backend.HttpClientExtensions.<ParseResponseBodyAsJsonAsync>d__2`1.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.Backend.HttpClientExtensions.<GetJsonAsync>d__0`1.MoveNext()`

Diagnostics ID: B2AAA3C5-E822-4735-B453-55B44408095B/20200212103721

Expected behaviour: Docker Desktop starts successfully after installation
Actual behaviour: Docker Desktop crashes when trying to start

From what I've seen on the Internet, the issue appeared in the past as well, but none one of the solutions described there worked (reinstalling the app, deleting all leftover folders and registry files, setting the primary DNS to 8.8.8.8 etc.)

Windows Version: Windows 10 Enterprise Version 1709 OS Build 16299.1625
Docker Desktop Version: 2.2.0.3
Virtualized Windows: No

@RobertNickRevnic RobertNickRevnic changed the title Get http://unix/engine/daemon.json: net/http: request canceled (Client.Timeout exceeded while awaiting headers Get http://unix/engine/daemon.json: net/http: request canceled (Client.Timeout exceeded while awaiting headers) Feb 12, 2020
@Murik
Copy link

Murik commented Feb 14, 2020

the same issue after update to Docker Desktop 2.2.0.3(42716)

501B2A25-F8CF-4A37-A6EA-18B4EFFB44CA/20200213112419

Docker.Core.HttpBadResponseException:
unable to fetch daemon.json: Get http://unix/engine/daemon.json: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
в Docker.Backend.HttpClientExtensions.d__2`1.MoveNext()

Version: 2.2.0.3 (42716)
Channel: stable
Sha1: e11f25edf9f955239c922a0251699b23aaf37984
Started on: 2020/02/13 14:22:23.325
Resources: C:\Program Files\Docker\Docker\resources
OS: Windows 10 Enterprise
Edition: Enterprise
Id: 1709
Build: 16299
BuildLabName: 16299.637.amd64fre.rs3_release_svc.180808-1748

@Murik
Copy link

Murik commented Feb 14, 2020

i temporary fixed this problem by Disable "Windows Subsystem for Linux"

PowerShell command:
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux

@theryansmith
Copy link

Same problem here.

@RobertNickRevnic
Copy link
Author

RobertNickRevnic commented Feb 17, 2020

I temporarily solved the problem by downgrading Docker Desktop to 2.1.0.5. You can download older stable versions from here: https://docs.docker.com/docker-for-windows/release-notes/

@casnitker
Copy link

casnitker commented Feb 27, 2020

I was also able to stop docker from crashing with disabling Windows subsystem for Linux. Unfortunately, I need that for the ubuntu instance I am running. I also can't seem to roll back because I have a shared drive that wasn't able to get working with the old version 2.1.0.5. Any ideas for a better fix?

@eeroniemi
Copy link

Ran into this same issue. I need Docker with WSL so only way to fix this problem was to uninstall Docker Desktop and re-install version 2.1.0.5.

@wayglem
Copy link

wayglem commented Mar 27, 2020

I have the same problem with 2.2.0.4. Downgrading to 2.1.0.5 fixed the issue

@docker-robott
Copy link
Collaborator

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

@williscool
Copy link

this is still happening on a fresh upgrade to Build 2004

Version: 2.3.0.4 (46911)
Channel: stable
Sha1: d4f5fcf98140180eeef00e02c1c8bb0ad69e35d3
Started on: 2020/07/30 13:57:32.418
Resources: C:\Program Files\Docker\Docker\resources
OS: Windows 10 Pro
Edition: Professional
Id: 2004
Build: 19041
BuildLabName: 19041.1.amd64fre.vb_release.191206-1406

@Legorooj
Copy link

Legorooj commented Aug 8, 2020

@williscool I got the same issue. I opened my WSL shell, rebooted docker, and it worked.

@masters3d
Copy link

Same issue Version: 2.3.0.4 (46911)

@HankFit247
Copy link

Just happeend to me as well.

13C54427-3885-420C-ACA4-5D1CB72ACBBD/20200829083122

Docker.Core.HttpBadResponseException:
unable to fetch daemon.json: Get http://unix/engine/daemon.json: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
at Docker.Core.Logging.ClientExceptionInterceptor.d__0.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Core\Logging\ClientExceptionInterceptor.cs:line 17
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Docker.Core.Logging.LoggingMessageHandler.d__4.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Core\Logging\LoggingMessageHandler.cs:line 37
--- 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.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.Core.HttpClientExtensions.d__0`1.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Core\HttpClientExtensions.cs:line 16
--- 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.ApiServices.LifecycleClient.d__10.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\LifecycleClient.cs:line 124
--- 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.LinuxkitDaemonStartup.d__5.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Desktop\LinuxkitDaemonStartup.cs:line 32
--- 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.Engines.WSL2.LinuxWSL2Engine.d__24.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Desktop\Engines\WSL2\LinuxWSL2Engine.cs:line 152
--- 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.ApiServices.StateMachines.TaskExtensions.d__0.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\TaskExtensions.cs:line 29
--- 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.ApiServices.StateMachines.StartTransition.d__5.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 67
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Docker.ApiServices.StateMachines.StartTransition.d__5.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 92

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Sep 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests