Closed plleg closed 3 years ago
Same here!
I have a similar issue where docker is hanging after upgrading to 10.0.19555
Same here,
Same here. My log is identical to @rmja
I think this is related to https://github.com/microsoft/WSL/issues/4860
same here
I am having same issues - same environment - and Failed to check wsl-bootstrap version: exit code: 1
reported several days ago- no response as yet
@tim-pluralgroup this looks a lot like microsoft/WSL#4860 however it’s hard to tell without more information.
edit: sorry wrong ticket link, fixed now
I disabled automatic init mode for all Docker services and my problems have disappeared. In order to init WLS2 and docker with no problems was init "docker desktop" after Windows 10 boot. Even thought a new docker version was released yesterday and it looks that kind of problems with WLS2 seems solved. ( anyways I keep Docker disabled on boot)
I followed @jmar5439's recommendation: Stop "Docker Desktop Service" (in services.msc
). Start "Docker Desktop" (version 2.2.0.5 with engine 19.03.8). It works perfectly.
Microsoft Windows [Version 10.0.19587.1000]
My error log report has strange German, English, Chinese language mixture:
Docker.Core.Backend.BackendException:
Failed to check wsl-bootstrap version: exit code: 1
stdout(utf8):
stdout(unicode):
stderr (utf8): Der Remoteprozeduraufruf ist fehlgeschlagen und wurde nicht ausgef�hrt.
stderr (unicode): 敄敒潭整牰穯摥牵畡牦晵椠瑳映桥杬獥档慬敧湵畷摲楮档⁴畡杳晥棼瑲മ
bei Docker.Core.Pipe.NamedPipeClient.<TrySendAsync>d__5.MoveNext()
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
bei Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters)
bei Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean withNotifications)
bei Docker.Actions.<>c__DisplayClass26_0.<StartAsync>b__0()
bei Docker.ApiServices.TaskQueuing.TaskQueue.<>c__DisplayClass18_0.<.ctor>b__1()
System.InvalidOperationException:
Failed to check wsl-bootstrap version: exit code: 1
stdout(utf8):
stdout(unicode):
stderr (utf8): Der Remoteprozeduraufruf ist fehlgeschlagen und wurde nicht ausgef�hrt.
stderr (unicode): 敄敒潭整牰穯摥牵畡牦晵椠瑳映桥杬獥档慬敧湵畷摲楮档⁴畡杳晥棼瑲മ
bei Docker.Backend.ContainerEngine.WslEngine.WslOneShotResult.LogAndThrowIfUnexpectedExitCode(String prefix, ILogger log, Int32 expectedExitCode)
bei Docker.Backend.ContainerEngine.WslEngine.get_IsDistroDeployed()
bei Docker.Backend.ContainerEngine.WslEngine.DoStart(Settings settings, String daemonOptions, Credential credential)
bei Docker.Backend.ContainerEngine.WslEngine.Start(Settings settings, String daemonOptions, Credential credential, Boolean retry)
bei Docker.Backend.ContainerEngine.WslEngine.Start(Settings settings, String daemonOptions, Credential credential, Boolean retry)
bei Docker.Backend.ContainerEngine.WslEngine.Start(Settings settings, String daemonOptions, Credential credential)
bei Docker.Backend.BackendNamedPipeServer.<Run>b__8_2(Object[] args)
bei Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.<Register>b__0(Object[] parameters)
bei Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)
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
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
Expected behavior
Docker Desktop starts up
Actual behavior
Docker Desktop crashes when trying to start up
Information
Steps to reproduce the behavior