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
Failed to start the Docker Engine after update to last version 4.19.0 (getting WSL version: exit status 0xffffffff) #13445
Comments
Hi @jlumbierres, sorry to hear you found a problem and thanks for filing the report. Could you please provide the output of executing Thanks! |
Initial analysis shows Docker Desktop failed to start, presumably because it had trouble determining the version of WSL on the host. The com.docker.backend logs show:
This WSL version check was added in Docker Desktop 4.19. |
I have the same problem :( |
Sorry to hear that @jakubvedral; can you please provide the output of Thanks! |
Sorry to say this but docker its already in function |
Thanks @jlumbierres; do you mean it works now (i.e., it started successfully)? If so, did you change anything on the host? |
I solved it by downgrading to 4.18 @ctalledo Output of:
is:
|
Hi @jakubvedral, What does the output of Context: Docker Desktop 4.19 checks for the WSL version using the Also, if you update WSL to the latest version (e.g., |
I have the same problem
|
sorry for the delay. It is quite useless output, but here it is :) :
I will try the update and report back. Thank you |
Thanks @jakubvedral. Based on the output for
Thanks. Yes, updating WSL ( |
My WSL was up to date so It also seems to load on first try if it's been working and you do a |
Thanks @jaimeburnap for chiming in. If your WSL was up to date and |
@ctalledo OK. This has been the only issue I've had so far and it's been intermittent. Are there any tickets related to that that I can take a look at? Thank you. |
Hi @jaimeburnap, Going back to this comment you made earlier:
If WSL is up to date, when
But earlier you indicated that it reports:
This means WSL is not up to date. To update it, do the following please:
Give that a try and see if that works. Thanks! |
FYI, the upcoming Docker Desktop 4.20 will have a fix so it better deals with hosts with old versions of WSL (i.e., where |
Closing as issue is fixed in DD 4.20. Please re-open if you continue to see the same problem. Summary: DD 4.19 has a bug where it fails to start in Windows hosts with old WSL versions (where command In such hosts, DD 4.19 may fail to start and the log file at DD 4.20 includes a fix that allows it better deal with this scenario so it won't fail to start. |
Actual behavior
Docker stopped.
And it shows this Erros
System.Exception:
2 errors occurred:
* starting keep alive in the data distro: waiting for wsl-keepalive to be ready: running wsl-keepalive in "docker-desktop-data": exit status 0xffffffff
* checking if isocache exists: CreateFile \wsl$\docker-desktop-data\isocache: No se encuentra el nombre de red especificado.
en Docker.Engines.WSL2.LinuxWSL2Engine.d__10.MoveNext() en C:\workspaces\PR-21718\src\github.com\docker\pinata\win\src\Docker.Engines\WSL2\LinuxWSL2Engine.cs:línea 93
--- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción ---
en System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
en Docker.ApiServices.StateMachines.TaskExtensions.d__0.MoveNext() en C:\workspaces\PR-21718\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\TaskExtensions.cs:línea 29
--- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción ---
en System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
en Docker.ApiServices.StateMachines.StartTransition.d__7.MoveNext() en C:\workspaces\PR-21718\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:línea 79
--- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción ---
en System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
en Docker.ApiServices.StateMachines.StartTransition.d__7.MoveNext() en C:\workspaces\PR-21718\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:línea 108
--- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción ---
en System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
en Docker.ApiServices.StateMachines.EngineStateMachine.d__17.MoveNext() en C:\workspaces\PR-21718\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\EngineStateMachine.cs:línea 97
--- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción ---
en System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
en Docker.Engines.Engines.d__25.MoveNext() en C:\workspaces\PR-21718\src\github.com\docker\pinata\win\src\Docker.Engines\Engines.cs:línea 126
Expected behavior
Docker running
Information
Output of
& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check
com.docker.diagnose.exe.log
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: