Skip to content

Upgraded from 4.15.0 to 4.16.1 docker stuck in starting mode forever #13165

Closed
Closed
Upgraded from 4.15.0 to 4.16.1 docker stuck in starting mode forever#13165
Labels
lifecycle/locked

Description

@jeffrozica
jeffrozica
opened on Jan 13, 2023
  • I have tried with the latest version of Docker Desktop
  • I have tried disabling enabled experimental features
  • I have uploaded Diagnostics
  • Diagnostics ID:

Actual behavior

Expected behavior

Information

  • Windows Version:
  • Docker Desktop Version:
  • WSL2 or Hyper-V backend?
  • Are you running inside a virtualized Windows e.g. on a cloud server or a VM:

Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check

Steps to reproduce the behavior

  1. ...
  2. ...

Activity

  1. jeffrozica commented on Jan 13, 2023

    @jeffrozica
    jeffrozica
    on Jan 13, 2023
    Author

    I just upgraded from docker desktop for windows version 4.15.0 to 4.16.1 on my laptop with windows 11 running wsl2 and ubuntu. After upgrading docker desktop is stuck in starting mode forever... It will not start and is hung. It worked great in version 4.15.0 and prior versions.... I downloaded 4.16.1 and tried install again, but did not work. I rebooted my laptop and that did not work. I do a lot of development and I am dead in the water. The only way I can see to fix this is to uninstall 4.16.1 and reinstall 4.15.0 and see if I can get it back up and running, but that's a lot of work...

  2. feynmanliang commented on Jan 13, 2023

    @feynmanliang
    feynmanliang
    on Jan 13, 2023

    This happened to me as well on both 4.16.0 and 4.16.1, but not 4.15.0. Possible bug in $USER interpolation?

    From %APPDAATA%/Local/Docker/log.txt

    [2023-01-13T21:37:15.327970500Z][com.docker.backend.exe][I] WSLEngine: start handler error exit: 1 error occurred:
[2023-01-13T21:37:15.328328600Z][GoBackendProcess][I] 	* provisioning docker WSL distros: deploying "docker-desktop": preparing directory "C:\\Users\\<USER>\\AppData\\Local\\Docker\\wsl\\distro" for distro "docker-desktop": decompressing "C:\\Users\\<USER>\\AppData\\Local\\Docker\\wsl\\distro": 1 error occurred:
[2023-01-13T21:37:15.328328600Z][GoBackendProcess][I] 	* decompressing file "C:\\Users\\<USER>\\AppData\\Local\\Docker\\wsl\\distro": The parameter is incorrect.
[2023-01-13T21:37:15.328328600Z][com.docker.backend.exe][W] (022eb604) 7b25e335-BackendAPI S->C 750ed8b2-GoBackendClient-CSharp POST /wsl/engine/start (4.3219861s): 1 error occurred:
[2023-01-13T21:37:15.328835600Z][GoBackendProcess][I] 	* provisioning docker WSL distros: deploying "docker-desktop": preparing directory "C:\\Users\\<USER>\\AppData\\Local\\Docker\\wsl\\distro" for distro "docker-desktop": decompressing "C:\\Users\\<USER>\\AppData\\Local\\Docker\\wsl\\distro": 1 error occurred:
[2023-01-13T21:37:15.328835600Z][GoBackendProcess][I] 	* decompressing file "C:\\Users\\<USER>\\AppData\\Local\\Docker\\wsl\\distro": The parameter is incorrect.

  3. jeffrozica commented on Jan 13, 2023

    @jeffrozica
    jeffrozica
    on Jan 13, 2023
    Author

    This happened to me as well on both 4.16.0 and 4.16.1, but not 4.15.0. Possible bug in $USER interpolation?

    From %APPDAATA%/Local/Docker/log.txt

    [2023-01-13T21:37:15.327970500Z][com.docker.backend.exe][I] WSLEngine: start handler error exit: 1 error occurred:
[2023-01-13T21:37:15.328328600Z][GoBackendProcess][I] 	* provisioning docker WSL distros: deploying "docker-desktop": preparing directory "C:\\Users\\<USER>\\AppData\\Local\\Docker\\wsl\\distro" for distro "docker-desktop": decompressing "C:\\Users\\<USER>\\AppData\\Local\\Docker\\wsl\\distro": 1 error occurred:
[2023-01-13T21:37:15.328328600Z][GoBackendProcess][I] 	* decompressing file "C:\\Users\\<USER>\\AppData\\Local\\Docker\\wsl\\distro": The parameter is incorrect.
[2023-01-13T21:37:15.328328600Z][com.docker.backend.exe][W] (022eb604) 7b25e335-BackendAPI S->C 750ed8b2-GoBackendClient-CSharp POST /wsl/engine/start (4.3219861s): 1 error occurred:
[2023-01-13T21:37:15.328835600Z][GoBackendProcess][I] 	* provisioning docker WSL distros: deploying "docker-desktop": preparing directory "C:\\Users\\<USER>\\AppData\\Local\\Docker\\wsl\\distro" for distro "docker-desktop": decompressing "C:\\Users\\<USER>\\AppData\\Local\\Docker\\wsl\\distro": 1 error occurred:
[2023-01-13T21:37:15.328835600Z][GoBackendProcess][I] 	* decompressing file "C:\\Users\\<USER>\\AppData\\Local\\Docker\\wsl\\distro": The parameter is incorrect.

    Thanks for your response. I uninstalled v4.16.1 and am in the process of re-installing v4.15.0. Hopefully this will work for me.

  4. jeffrozica commented on Jan 13, 2023

    @jeffrozica
    jeffrozica
    on Jan 13, 2023
    Author

    I just installed 4.15.0 and now I am getting failed to start. Frustrated.

  5. jeffrozica commented on Jan 13, 2023

    @jeffrozica
    jeffrozica
    on Jan 13, 2023
    Author

    I uninstalled docker docktop, then rebooted my laptop and then re-installed docker desktop for windows version 4.15.0 and I am now back up and running. I am rebuilding all of my docker images. Many thanks for the help. I hope version 4.16.1 is fixed as I cannot upgrade until it is.

  6. jafin commented on Jan 14, 2023

    @jafin
    jafin
    on Jan 14, 2023

    Similar issue,
    Issue: updating 4.15 to 4.16.1 stuck on Starting Docker.
    TempFix: Reverting to 4.15 resolved the issue.

    I could not see anything in the log.txt about <USER> per @feynmanliang comment.
    Feel free to let me know if there is anything else I can post to help troubleshoot.

    • Windows 11 22H2
    • WSL2 backend

    Things tried:

    • Uninstalling/reinstalling docker.
    • Updating wsl --update

  7. Hombre2014 commented on Jan 14, 2023

    @Hombre2014
    Hombre2014
    on Jan 14, 2023

    The same problem here. I upgraded from 4.10 to 4.16.1 and it stuck in Starting forever. I uploaded the diagnostics to Docker. My diagnostic ID is: C84E282B-A40C-4C57-8B55-2C7E146FBACD/20230114112020
    I am using Windows 10 Pro latest package.

  8. thaJeztah commented on Jan 14, 2023

    @thaJeztah
    thaJeztah
    on Jan 14, 2023
    Member

    This happened to me as well on both 4.16.0 and 4.16.1, but not 4.15.0. Possible bug in $USER interpolation?

    From %APPDAATA%/Local/Docker/log.txt

    [2023-01-13T21:37:15.327970500Z][com.docker.backend.exe][I] WSLEngine: start handler error exit: 1 error occurred:
[2023-01-13T21:37:15.328328600Z][GoBackendProcess][I] 	* provisioning docker WSL distros: deploying "docker-desktop": preparing directory "C:\\Users\\<USER>\\AppData\\Local\\Docker\\wsl\\distro" for distro "docker-desktop": decompressing "C:\\Users\\<USER>\\AppData\\Local\\Docker\\wsl\\distro": 1 error occurred:
[2023-01-13T21:37:15.328328600Z][GoBackendProcess][I] 	* decompressing file "C:\\Users\\<USER>\\AppData\\Local\\Docker\\wsl\\distro": The parameter is incorrect.
[2023-01-13T21:37:15.328328600Z][com.docker.backend.exe][W] (022eb604) 7b25e335-BackendAPI S->C 750ed8b2-GoBackendClient-CSharp POST /wsl/engine/start (4.3219861s): 1 error occurred:
[2023-01-13T21:37:15.328835600Z][GoBackendProcess][I] 	* provisioning docker WSL distros: deploying "docker-desktop": preparing directory "C:\\Users\\<USER>\\AppData\\Local\\Docker\\wsl\\distro" for distro "docker-desktop": decompressing "C:\\Users\\<USER>\\AppData\\Local\\Docker\\wsl\\distro": 1 error occurred:
[2023-01-13T21:37:15.328835600Z][GoBackendProcess][I] 	* decompressing file "C:\\Users\\<USER>\\AppData\\Local\\Docker\\wsl\\distro": The parameter is incorrect.

    👋 I work at Docker (but not on the Docker Desktop team); I think the <USER> should be unrelated to the issue; it looks like that's part of code that obfuscates personal data in logs (to prevent personal data being included in diagnostic reports). It seems a bit premature to obfuscate the local logs though, so perhaps I should ask the Desktop team if it would be better to obfuscate the data only when generating a diagnostic report (not for the local logs), or at least a more descriptive placeholder (<REDACTED_USER>).

  9. Hombre2014 commented on Jan 14, 2023

    @Hombre2014
    Hombre2014
    on Jan 14, 2023

    In my case, even 4.14.1 did not work and experienced the same freezing. I had to go back to 4.10.1. Did not try any in-between versions.

  10. zejji commented on Jan 14, 2023

    @zejji
    zejji
    on Jan 14, 2023

    I experienced the same issue with Docker Desktop 4.16.1 not starting after an upgrade from 4.15.0. I'm running on Windows 10 Pro with WSL 2 integration.

    The only solution was completely uninstalling Docker Desktop, restarting and then reinstalling 4.15.0, after which everything works normally again.

  11. kng commented on Jan 14, 2023

    @kng
    kng
    on Jan 14, 2023

    Updated from 4.14.? to 4.16.1 and got the same issue, downgrade to 4.15.0 did not work, 4.14.1 works.
    Cleaned up all appdata and reboot between tries.

  13. podling0ne commented on Jan 14, 2023

    @podling0ne
    podling0ne
    on Jan 14, 2023

    I had the same issue with a fresh install of 4.16.1, tried 4.16.0 and same again. I tried 4.15.0, and then docker desktop asked me to download the update of wsl2. I did it and it worked fine.
    So i tried to update to 4.16.1, and it finally worked for me.
    Don't know if it would help.
    I'm on Windows 11 familly .

  14. BlueAlder commented on Jan 16, 2023

    @BlueAlder
    BlueAlder
    on Jan 16, 2023

    Same thing happened to me, uninstalled and tried to reinstall 4.16.1 and got installation errors. Ended up just reverting to install 4.16.0 which is working so far.

  15. amoisis commented on Jan 17, 2023

    @amoisis
    amoisis
    on Jan 17, 2023
    • wsl --unregister docker-desktop-data
    • wsl --unregister docker-desktop
    • Uninstall Docker for Windows
    • Install Docker for Windows

    Not sure if the uninstall was required but it works again.
    Found from here https://stackoverflow.com/questions/71702448/docker-daemon-not-running-on-windows-11

  16. 58 remaining items

  17. malcolmradelet commented on Feb 3, 2023

    @malcolmradelet
    malcolmradelet
    on Feb 3, 2023

    I am running 4.16.3 and currently watching the "Docker Desktop stopping..." message for over 5 minutes now. I don't think its going anywhere. Does not appear to be resolved. What information can I send to assist?

  18. kenlfg commented on Feb 7, 2023

    @kenlfg
    kenlfg
    on Feb 7, 2023

    Can confirm 4.16.3 is having this issue. Upgraded from 4.15. As soon as I did, that and the Kubernetes service wouldn't start. Restart didn't help (in fact it's worse...reports the WSL2 back-end failed to start).

    OS Reboot helped (Docker started, Kubernetes failed). Restart in-app (via the Troubleshooting menu) resulted in both services failing to start (and the WSL2 back-end failure message).

    Resetting to factory settings did nothing to help.

    Thought it might be ransomware protection but there are no log entries from today.

    Restarting after the factory reset did not help either.

    Looking at the process, it seems like it's having a LOT of trouble getting com.docker.proxy.exe to start. It's constantly starting then suspending and killing the process. Note that this is a SECOND instance.

    See the bottom of the attached image:

    Screenshot 2023-02-06 203019

    The processes have no information attached (at least none that Process Explorer is displaying).

  19. kenlfg commented on Feb 7, 2023

    @kenlfg
    kenlfg
    on Feb 7, 2023

    Note that I'm on Windows 11 22H2, up to date with Windows Updates except for KB50223650 (2023-01 Cumulative Update).

    Going to downgrade for now as I've got work to do. :)

  20. guruprasanthe commented on Mar 2, 2023

    @guruprasanthe
    guruprasanthe
    on Mar 2, 2023

    I faced the same issue. I uninstalled it and opened the installer as admin. After the installation, docker is running fine.

  21. allenyllee commented on Mar 9, 2023

    @allenyllee
    allenyllee
    on Mar 9, 2023

    Update to 4.17.0 still have the same issue, and I got an error message:

    Snipaste_2023-03-09_17-20-21

    Diagnostics ID:
    F396B5CE-28DB-447C-AF09-E39E9E84C7AC/20230309091428

  22. garystafford commented on Mar 14, 2023

    @garystafford
    garystafford
    on Mar 14, 2023

    Same issue. The previous version was running fine. Updated to 4.17.0, and it hangs on starting. Restarting and/or rebooting my Mac makes no difference. How is this issue possibly closed given all the issues reported here!?

  23. garystafford commented on Mar 14, 2023

    @garystafford
    garystafford
    on Mar 14, 2023

    If a simple upgrade doesn't work for multiple versions, there is a larger issue.

  24. stevehipwell commented on Mar 14, 2023

    @stevehipwell
    stevehipwell
    on Mar 14, 2023

    Same issue here; both upgrading to v4.17.0 and on a completely clean install of v4.17.0.

  25. sjavaid2T commented on Mar 31, 2023

    @sjavaid2T
    sjavaid2T
    on Mar 31, 2023

    I'm using v4.17.0 and having the same issue. Everything was working fine till today when it randomly stopped working. Uninstalled docker and reinstalled and still same issue. The wsl --update command doesn't update anything. Is it something to do with WSL?

  26. laoda512 commented on Apr 2, 2023

    @laoda512
    laoda512
    on Apr 2, 2023

    I'm using v4.17.1 and having the same issue.

    All containers cannot be started and display an orange icon. docker ps -ls cannot print out the containers, but the ports for the containers have been allocated.

    Two years ago, when I updated Docker, all volumes and images were lost. Since then, I have been too afraid to update Docker without a good reason. However, I updated it today on a whim, and the result proved that updating Docker is the most dangerous and unrewarding thing in software development.

    （╯°□°）╯︵ ┻━┻
    （╯°□°）╯︵ ┻━┻
    （╯°□°）╯︵ ┻━┻

  27. joaodejesus commented on Apr 2, 2023

    @joaodejesus
    joaodejesus
    on Apr 2, 2023

    I have the same problema with v4.16.3. I tried reboot, reinstall, unregistering and nothing works for me. I'm going to downgrade and see if that works.

  28. sjavaid2T commented on Apr 5, 2023

    @sjavaid2T
    sjavaid2T
    on Apr 5, 2023

    So for me, the issues seemed to be that WSL stopped working after waking my laptop from sleep. I tried opening my Ubuntu terminal but it was hanging. I used this solution to restart WSL and that in turned fixed my docker issues:

    https://stackoverflow.com/questions/70567543/cant-restart-wsl2-lxssmanager-hangs-in-stopping-state-how-to-restart

  29. docker-robott commented on May 5, 2023

    @docker-robott
    docker-robott
    on May 5, 2023
    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.

    /lifecycle locked

  30. Imagedocker
    locked and limited conversation to collaborators on May 5, 2023
  31. Imagedocker-robott
    added
    lifecycle/locked
    on May 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/locked

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions