Docker Can't be opened - known Mac issue

[clehman7]

I rebooted my computer and upon restarting I received the following pop-up. Evidently this is a known issue. Fix startup issue for Mac | Docker Docs

I tried cancelling it but it just keeps re-appearing. When I attempt to open Docker I receive the following pop-up.

This blog provides possible courses of action but it depends on what version you are running.

Incident Update: Docker Desktop for Mac | Dockerffu5_gcl_auMTcxNjA1MDE0Ny4xNzM3MzE2NjMw_gaMzkxMzE0NjkwLjE3MzczMTY0MjA._ga_XJWPQMJYHQ*MTczNzMxNjQxOS4xLjEuMTczNzMxNjYyOS42MC4wLjA.

Does Quantrocket have a recommended course of action? What can be done to ensure files are not lost?

Please advise.

[Brian]

Your data is stored in Docker volumes, so it's important that those don't get deleted. I would avoid completely trashing/uninstalling Docker for fear of volumes getting deleted. If you can open Docker (which it sounds like you can't), update Docker from within the app ("check for updates"). If you can't open Docker, download the newest version of Docker Desktop from here and install it, replacing the current version when prompted. Updating Docker in either of these ways is a normal upgrade activity that doesn't delete volumes.

[clehman7]

@Brian I am unable to open Docker so I downloaded the latest version. However, I continue to receive the “com.docker.vmnetd” pop up warning and it's preventing me from opening the new version of Docker I've downloaded. Are my existing volumes located in this file or can I delete it? My hope is that by deleting the “com.docker.vmnetd” file I'll be able to successfully upgrade. Thanks for the help.

[Brian]

The following commands from this GitHub issue can be safely run (and ignored if they fail):

sudo pkill '[dD]ocker'

sudo launchctl bootout system /Library/LaunchDaemons/com.docker.vmnetd.plist

sudo launchctl bootout system /Library/LaunchDaemons/com.docker.socket.plist

sudo rm -f /Library/PrivilegedHelperTools/com.docker.vmnetd

sudo rm -f /Library/PrivilegedHelperTools/com.docker.socket

[clehman7]

@Brian appreciate the help. I ran those commands and was then able to successfully restart Docker. None of my documents were lost. Thank you.