Docker Unexpected error #14034

Activity

1. Amulya2528

   added

   needs-triage

   on Apr 25, 2024
2. docker-robot

   added

   version/4.29.0

   on Apr 25, 2024
3. hblovo commented on Apr 27, 2024

   

   hblovo

   on Apr 27, 2024

   Last edited by hblovo

   More actions

   Getting back to an old version might help because I just saw your problem recently based on the error information.

   👍React with 👍1Reacted by Vaibhav Agarwal
4. interplexed commented on Apr 28, 2024

   

   interplexed

   on Apr 28, 2024

   Last edited by interplexed

   More actions

   For me this appeared after upgrading Docker Desktop to v4.29.0 (latest) on Windows 11 23H2 (22631.3447) within the last week. After the error message, re-running the program results in the same error message. Using task manager to shutdown all docker-related processes and re-run, appears to work.
   FWIW, it feels like a timeout based on internet connection. I'm setting my laptop to hibernate with it's not-so-great VPN connection up... it's as if when I disconnect the VPN, Docker Desktop loads normally.
   Diagnostics ID: 57D5AE4A-0D1B-4ABD-9746-CB4530A08E0D/20240428084301

   👍React with 👍2Reacted by Sahapap and Irfandy J
5. neonima

   added

   area/WSL2

   on Apr 29, 2024
6. samir-puranik commented on Apr 29, 2024

   

   samir-puranik

   on Apr 29, 2024

   Last edited by samir-puranik

   More actions

   I am also experiencing the same issue. Diagnostics ID: 49DC9064-604D-494C-ACB0-236581DCA481/20240429165804

   docker --version
   Docker version 26.0.0, build 2ae903e
   
   wsl --list
   Windows Subsystem for Linux Distributions:
   docker-desktop-data (Default)
   docker-desktop
   
7. samir-puranik commented on Apr 29, 2024

   

   samir-puranik

   on Apr 29, 2024

   Last edited by samir-puranik

   More actions

   Getting back to an old version might help because I just saw your problem recently based on the error information.

   Tried this and confirming that this works. I uninstalled 4.29.0 and re-installed 4.28.0 and now it's working again

   👍React with 👍1Reacted by liumudj
8. liumudj commented on May 1, 2024

   

   liumudj

   on May 1, 2024

   More actions

   回退到之前版本有效
9. liumudj commented on May 1, 2024

   

   liumudj

   on May 1, 2024

   More actions

   https://docs.docker.com/desktop/release-notes/#docker-desktop-community-2501
10. romancristinel commented on May 1, 2024

    

    romancristinel

    on May 1, 2024

    More actions

    Disabling the auto start on system start (via Task Manager / Startup apps) for Docker Desktop fixed it for me .
11. senina4 commented on May 4, 2024

    

    senina4

    on May 4, 2024

    Last edited by senina4

    More actions

    This work for me:

    wsl --unregister docker-desktop 
    

    Restart Docker Desktop

    (edited: this command won't delete your data)

    👍React with 👍131Reacted by R., stv, Max Eriksson, Sean Chang, WiFiExpertAP, Sergio, Fhun, Wojciech Bandzerewicz, Андрей, yaolh and 121 more

    🎉React with 🎉33Reacted by Fhun, Andrii Lagovskyi, Freddy Barragán, Ousama Esbel, Bartosz Kaczmarek, Issac, Koushik Seal, Dragos Catalin, WANDERSON ALVES RIBEIRO, Brian and 23 more

    😕React with 😕8Reacted by Jihan Fu, Dragos Catalin, onvo, Thom, BestAssist, Evandson Cruz, Chitsanupong Paenyoi and Benjamin

    ❤️React with ❤️42Reacted by Fhun, Weslley N.Dutra, yaolh, Andrii Lagovskyi, Andrew, Ayomide Agbaje, Floris, Freddy Barragán, Ousama Esbel, Bartosz Kaczmarek and 32 more

    🚀React with 🚀17Reacted by WANDERSON ALVES RIBEIRO, Brian, Mehmet Salih YALDIZ, Surdu Constantin, Yahor Babrouski, carlos, onvo, BestAssist, przemokon, Trevor Sullivan and 7 more

    👀React with 👀2Reacted by kengkreingkrai and Vlad Moiseienko
12. xszefo commented on May 4, 2024

    

    xszefo

    on May 4, 2024

    More actions

    @senina4 , it also works for me, thanks! :)

    👍React with 👍6Reacted by Sean Chang, pengyusi, BestAssist, Evandson Cruz, dyexlzc and blueeeeblue
13. smartercow commented on May 6, 2024

    

    smartercow

    on May 6, 2024

    More actions

    This work for me:

    wsl --unregister docker-desktop
    wsl --unregister docker-desktop-data
    

    Restart Docker Desktop

    Same

    👍React with 👍12Reacted by Freddy Barragán, Delamater, Baciu Vlad-Eusebiu, Surdu Constantin, henriqueholtztraycorp, Evandson Cruz, hechaoqi123, hunsly, kengkreingkrai, Aleksandr Chaplygin and 2 more

    👎React with 👎1Reacted by morimoto
14. bsousaa

    added

    status/triage

    and removed

    needs-triage

    on May 6, 2024
15. 9 remaining items

    Load more

16. nikosvil commented on Jul 24, 2024

    

    nikosvil

    on Jul 24, 2024

    Last edited by nikosvil

    More actions

    This work for me:

    wsl --unregister docker-desktop
    wsl --unregister docker-desktop-data
    

    Restart Docker Desktop

    Had the same issue on 4.32.0, those commands fixed it. Thanks!
17. nikolausmoll commented on Aug 16, 2024

    

    nikolausmoll

    on Aug 16, 2024

    More actions

    This work for me:

    wsl --unregister docker-desktop
    wsl --unregister docker-desktop-data
    

    Restart Docker Desktop

    warning！this will clean all your images and containers
    yeah, I don't know why the warning is not part of the original post...

    anyway, did not solve it for me for Docker Desktop 4.33.1 (162079) - have to start the Docker software manually, but that sucks.

    👍React with 👍1Reacted by SAP Sentinel
18. lorenrh commented on Aug 30, 2024

    

    lorenrh

    on Aug 30, 2024

    Member

    More actions

    4.34.0 has been released with a fix for this issue, more information o the release notes.

    I'll be closing this issue, but if the problem persists please open a fresh issue!
19. lorenrh

    closed this as completedon Aug 30, 2024
20. andreaswrife commented on Aug 30, 2024

    

    andreaswrife

    on Aug 30, 2024

    Last edited by andreaswrife

    More actions

    The issue persists.

    Updated from 4.33.1, being plagued with the the #13806 error.
    Now with 4.34.0 I get this issue. #14034
    Although the release notes indicate that this bug is fixed.

    I have tried the wsl --unregister quickfix without success.

    I am gonna play around with it a bit more, see if there is some setting I've changed..

    👍React with 👍8Reacted by Azsamot, harappa, Nick North, Phoebe Scaccia, arthackrc, Mattias Nordstrom, Nándor Sperl and ‽
21. vaibhavPH commented on Sep 2, 2024

    

    vaibhavPH

    on Sep 2, 2024

    More actions

    4.34.0 has been released with a fix for this issue, more information o the release notes.

    I'll be closing this issue, but if the problem persists please open a fresh issue!

    not fixed for me even in docker desktop 4.3.4
22. andrea-reale commented on Sep 2, 2024

    

    andrea-reale

    on Sep 2, 2024

    More actions

    Hey all - thanks for reporting that the problem persists with 4.34. Unfortunately, the fix introduced in 4.34 had itself a bug. Please, take a look at for a possible workaround #14294 (comment).

    Since this issue is now closed, please use #14294 for any further communication (and remember to include diagnostics!).
23. jeaneigsi commented on Sep 22, 2024

    

    jeaneigsi

    on Sep 22, 2024

    More actions

    This work for me:

    wsl --unregister docker-desktop
    wsl --unregister docker-desktop-data
    

    Restart Docker Desktop

    work perfectly thanks

    👍React with 👍3Reacted by hunsly, Jack Hong and Betsq9
24. java43wuyi commented on Oct 13, 2024

    

    java43wuyi

    on Oct 13, 2024

    More actions

    I reinstalled docker and followed Microsoft's instructions https://learn.microsoft.com/en-us/windows/wsl/install to install and start wsl2, then restarted docker. If there are any problems during the installation, check the Microsoft website https://learn.microsoft.com/en-us/windows/wsl/troubleshooting#installation-issues for solutions
25. Carlos-vargs commented on Nov 6, 2024

    

    Carlos-vargs

    on Nov 6, 2024

    More actions

    This work for me:

    wsl --unregister docker-desktop
    wsl --unregister docker-desktop-data
    

    Restart Docker Desktop

    warning！this will clean all your images and containers

    too late 😔
26. PatchFact commented on Dec 19, 2024

    

    PatchFact

    on Dec 19, 2024

    More actions

    For me the solution was disabling "use legacy mode" for cmd.exe. In my case, I had set up a shortcut to run a terminal command on startup which had this enabled and it affects all terminals (properties -> options -> legacy mode).

    You might have enabled this feature at some point before if none of the above fixes worked for you.

    👍React with 👍3Reacted by Pazaz, Valerii V. Shinkevich and Nesemis
27. ackvf commented on Jan 26, 2025

    

    ackvf

    on Jan 26, 2025

    More actions

    This work for me:

    wsl --unregister docker-desktop
    wsl --unregister docker-desktop-data
    

    Restart Docker Desktop

    warning！this will clean all your images and containers

    too late 😔

    Is it possible to reattach the images back to avoid the loss?
28. brazeiro63 commented on Feb 13, 2025

    

    brazeiro63

    on Feb 13, 2025

    Last edited by brazeiro63

    More actions

    The issue:
    running engine: waiting for the VM setup to be ready: starting WSL engine: bootstrapping in the main distro: running wsl-bootstrap: exit status 0xffffffff

    Is still present.

    Docker Desktop v4.38.0
    Diagnostic ID: 3710D364-1E7E-42DA-9D7D-C1DBAAE334D1/20250213155646

    Edição Windows 10 Pro
    Versão 22H2
    Instalado em ‎06/‎08/‎2023
    Compilação do SO 19045.5487
    Experiência Windows Feature Experience Pack 1000.19061.1000.0

    👍React with 👍4Reacted by David, Moyu, Alexa Despacito and Lars Jendrzejewski
29. docker-robot

    added

    version/4.38.0

    on Feb 13, 2025
30. Nesemis commented on Apr 13, 2025

    

    Nesemis

    on Apr 13, 2025

    Last edited by Nesemis

    More actions

    For me the solution was disabling "use legacy mode" for cmd.exe. In my case, I had set up a shortcut to run a terminal command on startup which had this enabled and it affects all terminals (properties -> options -> legacy mode).

    You might have enabled this feature at some point before if none of the above fixes worked for you.

    It worked for me. I checked 'Use legacy console' for hiding the terminal console for autorunning Syncthing, but now it made docker not work. If I disable legacy console, now the Syncthing terminal shows. Kinda annoying

    👍React with 👍1Reacted by Jihan Fu

    🎉React with 🎉1Reacted by Jihan Fu