Skip to content
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

Docker stuck on "Docker is starting" #2927

Closed
1 of 2 tasks
kevni111 opened this issue May 22, 2018 · 4 comments
Closed
1 of 2 tasks

Docker stuck on "Docker is starting" #2927

kevni111 opened this issue May 22, 2018 · 4 comments

Comments

@kevni111
Copy link

  • I have tried with the latest version of my channel (Stable or Edge)
  • I have uploaded Diagnostics
  • Diagnostics ID: 71668BE2-0083-4D6E-97ED-6E243CA9365D

Expected behavior

Docker status should change from starting to running

Actual behavior

Docker stuck at starting

Information

  • macOS Version: 10.13.4
@antontukhvatulin
Copy link

antontukhvatulin commented May 22, 2018

I have the same problem on macOS 10.13.4.

Diagnostics ID: 41EBE209-31B8-4459-B42F-134623D514B0

@YRM64
Copy link

YRM64 commented May 22, 2018

#2927 shares similarities to #482, 417, and #487.

And, I personally have experienced the exact same issue on MacOs 10.12.6, where Docker never ceased to finish starting.

#482 recommends a reset to factory default settings from the whale menu (for those that have access to the menu). If that doesn't work, then do a manual uninstall of Docker, and download the latest installer (for windows that installation website URL: https://docs.docker.com/Docker-for-windows/).

Guess what, this error also can occur if the Docker Daemon isn't running, which happened to be my case. Visual Studio Code alerted me to the fact that the daemon wasn't running. However, there are bugs out there that can also leave Docker in a frozen state of 'starting'.

Developers, I want to share with you some unique situations and challenges regarding this issue: @mmisztal1980 commented over a year ago, "it's impossible to use the "reset". All options in the "reset" pane are grayed out." And, he added that he had reinstalled Docker for windows "using the latest stable installer." "Same issue" (or same problem). He was asked to file a separate issue because he was told that his situation was unique. @mmisztal1980 responded, "I did, and it was closed out" (#487). He was then asked to:

He was advised to try the above steps to troubleshoot Docker. Docker was still stuck after @mmisztal undergone even additional sets of troubleshooting steps, other than what is stated above. You would be surprised to know that MSFT had to be brought in to help troubleshoot why Docker would'nt start. The verbal exchanges between all participants makes for an interesting story of courage and determination (#482). The exchanges are a depiction of the dedication and hard work that goes into building applications, and the active participants who all come together to make it work.

As it turned out, it was a third party software zerotier responsible, and after the uninstallation of zerotier, Docker started. Each use case is unique, and should be evaluated, and tested despite the similarities to other case files. The provision of information by the development community always encourages testing based upon the uniqueness of each use case.

For all practical purposes, generic responses by the community could be prefaced with 'generally speaking', so as to encourage testing, troubleshooting, keeping adequate records, and backing up our machines, so as to not lose precious work, or valuable time.

To follow the dialogue(s) of all participants of #482, to ascertain the strength and courage it requires to work in the field, and to ascertain a profound appreciation for the work that we do together in the field of developing, building, and deploying applications, view #482 at docker/for-win#482 (comment).

Happy Coding!

@docker-robott
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d 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

@docker-robott
Copy link
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.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jun 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants