I have been trying to understand this for a few hours now. Rather than solving the issue, I want to understand its source. Is this really a security concern? What is the reason behind this issue? Is there a satisfactory explanation for it? Or are the keys rotated that’s is used to sign Docker Desktop for Mac?
Guys I found the solution. you should check your macOS version. It should be 15.2.
And check your docker version to be 4.37.1. I hope you solve the problem : D
I deinstalled Docker months ago and today I got this message as well. WTF. I searched my Mac and there was nothing whi directs to something like Docker.
Some versions of Docker Desktop might fail to start or function with the following error message:
Malware Blocked. “com.docker.vmnetd” was not opened because it contains malware. This action did not harm your Mac.
Important
Those warnings are inaccurate. Docker Desktop is not affected by malware!
The root cause has been identified: some files in existing installations are incorrectly signed which can be fixed by copying correctly signed files from the Docker.app application bundle.
Workaround
Privileged users
Tip
If you face this issue, try the following procedure (requires root user access):
Quit Docker Desktop and check that no remaining docker processes are running using the Activity Monitor
Run the following commands:
#!/bin/bash # Stop the docker services echo “Stopping Docker…” sudo pkill ‘[dD]ocker’ # Stop the vmnetd service echo “Stopping com.docker.vmnetd service…” sudo launchctl bootout system /Library/LaunchDaemons/com.docker.vmnetd.plist # Stop the socket service echo “Stopping com.docker.socket service…” sudo launchctl bootout system /Library/LaunchDaemons/com.docker.socket.plist # Remove vmnetd binary echo “Removing com.docker.vmnetd binary…” sudo rm -f /Library/PrivilegedHelperTools/com.docker.vmnetd # Remove socket binary echo “Removing com.docker.socket binary…” sudo rm -f /Library/PrivilegedHelperTools/com.docker.socket # Install new binaries echo “Install new binaries…” sudo cp /Applications/Docker.app/Contents/Library/LaunchServices/com.docker.vmnetd /Library/PrivilegedHelperTools/ sudo cp /Applications/Docker.app/Contents/MacOS/com.docker.socket /Library/PrivilegedHelperTools/
Restart Docker Desktop
Non-privileged users
If the above instructions can’t be used because you don’t have root privileges or your Docker Desktop installation is managed by a Mobile Device Management solution, the above script needs to be executed by the MDM tool. Please contact your system administrators or Docker org owner for support.
I see that the discussions here confuse people and after everyone shares they had the same issue and share the same screenshots as many users already shared, the correct link to the issue and recommended solutions are hard to find. It makes new users share the same link again and again which is lost again or open a new issue instead of joining to the existing issue.
I’m going to close this topic and share the link again the last time to the issue on GitHub. Thank you for all the suggestions and reports, but please visit the issue on GitHub if you want to add more notes or get more, up-to-date information from the developers working hard on a permanent solution.
