"Fatal error Docker is already running" after 2.3.0.2 upgrade

[pinko-fowle]

• [X ] I have tried with the latest version of my channel (Stable or Edge)
• I have uploaded Diagnostics
• Diagnostics ID:

Expected behavior

Docker starts at startup

Actual behavior

"Fatal error Docker is already running" and no docker starts.

Information

• macOS Version: macOS Catalina 10.15.4

This is a duplicate of #4556 but you closed the issue before fixing or doing anything about it.

This is a super annoying issue for everyone on my team. We only just found how to fix it.

Please make the next installer fix this situation.

Also the fact that when this happens no Docker is left running is really frustrating.

Also please get rid of your very very annoying & frustrating Lockbot. This is an enormous roadblock to forward progress.

[stephen-turner]

The lockbot locks tickets that have already been closed. If the tickets are closed, no-one will see the comments anyway, so it would be pointless to allow people to write on them. In this case, the original reporter closed the issue having said that it was resolved.

[stephen-turner]

If you are still experiencing it, please describe the steps to reproduce. It's not common or we would have had hundreds of reports of it.

[pinko-fowle]

I am still experiencing this issue until I went & resolved it myself, using the same manual steps the author faced in #4556

I can continue to tell my team to all go follow these steps, but I fully believe this to be a regular issue faced, and one that Docker for mac ought to address & try to clean up itself. I don't know what version I was on before upgrading, so I'm taking #4556's good write up as the truth, that it was the upgrade to 2.3.0.2. Notably, like #4556, the key was that

I had several Docker entries, as well as a Docker Desktop entry in my Login Items for my User.

Deleting one of these fixed the issue for me. I would like the Docker installer to clean out whichever is deprecated. I left Docker Desktop and deleted Docker but I'm not sure which is the new & which is the old. I suspect this got changed at some point in the installer.

It's also weird that when this occurs, there's a modal about Docker already running, but then there is no Docker running, which seems like there is something wrong with the check Docker Desktop seems to have built-in at startup.

If the tickets are closed, no-one will see the comments anyway,

What makes you say that? Do you mean @docker won't see the comments? Because certainly anyone who happens upon an issue that pertains to them, even closed issues, would benefit from further contributions in that ticket. I'm not sure what you mean by no-one will see the comments. That is not my experience. My experience is that often users can help themselves & contribute more meaningful information to help others when tickets are not locked.

[yamagame]

I tried launch "Docker Desktop.app" with command line.

This command is "Fatal error Docker is already running".
$ "/Applications/Docker.app/Contents/MacOS/Docker Desktop.app/Contents/MacOS/Docker Desktop"

But this command is no problem.
$ "/Applications/Docker.app/Contents/MacOS/Docker Desktop.app/Contents/MacOS/Docker Desktop" --name=containers

--name=containers option is important.
"Docker Desktop.app" on osx finder's dock dose not have this option.

[docker-robott]

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

[docker-robott]

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