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
Comments
the same issue after update to Docker Desktop 2.2.0.3(42716) 501B2A25-F8CF-4A37-A6EA-18B4EFFB44CA/20200213112419 Docker.Core.HttpBadResponseException: Version: 2.2.0.3 (42716) |
i temporary fixed this problem by Disable "Windows Subsystem for Linux" PowerShell command: |
Same problem here. |
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/ |
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? |
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. |
I have the same problem with 2.2.0.4. Downgrading to 2.1.0.5 fixed the issue |
Issues go stale after 90 days of inactivity. Prevent issues from auto-closing with an 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. |
this is still happening on a fresh upgrade to Build 2004
|
@williscool I got the same issue. I opened my WSL shell, rebooted docker, and it worked. |
Same issue Version: 2.3.0.4 (46911) |
Just happeend to me as well. 13C54427-3885-420C-ACA4-5D1CB72ACBBD/20200829083122 Docker.Core.HttpBadResponseException: |
Closed issues are locked after 30 days of inactivity. 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. |
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)
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
The text was updated successfully, but these errors were encountered: