You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 19, 2026. It is now read-only.
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 reason for this warning is that some files in existing installations are incorrectly signed. This can be fixed by copying correctly signed files from the Docker.app application bundle.
To determine if you need to re-download and re-install Docker Desktop, please run the following steps.
Download the attached check.sh.txt file, rename it to check.sh and set the executable flag with chmod +x check.sh. (Caution: it is never a good idea to just run shell scripts downloaded from the internet. Please take a moment to review the script before executing it.)
Execute the following command to verify the binary in your Docker.app application bundle. The script will exit with 0 if the certificate was correctly verified:
$ ./check.sh /Applications/Docker.app/Contents/Library/LaunchServices/com.docker.vmnetd
-----------------------------------------------------------------
Certificate details for com.docker.vmnetd:
serial=3EC22E699630083A
subject=UID=9BNSXJN65R
CN=Developer ID Application: Docker Inc (9BNSXJN65R)
OU=9BNSXJN65R
O=Docker Inc
C=US
issuer=CN=Developer ID Certification Authority
OU=Apple Certification Authority
O=Apple Inc.
C=US
notBefore=Oct 2 16:46:37 2024 GMT
notAfter=Feb 1 22:12:15 2027 GMT
-----------------------------------------------------------------
com.docker.vmnetd is signed with a correct certificate
You can also verify files in the /Library/PrivilegedHelperTools folder with: ./check.sh /Library/PrivilegedHelperTools/com.docker.vmnetd and sudo ./check.sh /Library/PrivilegedHelperTools/com.docker.socket
If any of the above commands fail to verify the certificate, you have to re-download and re-install Docker Desktop
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 servicesecho"Stopping Docker..."
sudo pkill '[dD]ocker'# Stop the vmnetd serviceecho"Stopping com.docker.vmnetd service..."
sudo launchctl bootout system /Library/LaunchDaemons/com.docker.vmnetd.plist
# Stop the socket serviceecho"Stopping com.docker.socket service..."
sudo launchctl bootout system /Library/LaunchDaemons/com.docker.socket.plist
# Remove vmnetd binaryecho"Removing com.docker.vmnetd binary..."
sudo rm -f /Library/PrivilegedHelperTools/com.docker.vmnetd
# Remove socket binaryecho"Removing com.docker.socket binary..."
sudo rm -f /Library/PrivilegedHelperTools/com.docker.socket
# Install new binariesecho"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
If that still doesn't work, download one of the currently supported release from the Release notes, re-install the application and then finally re-apply step 2.
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.
Homebrew users
If you’ve installed Docker Desktop with Homebrew, you can update it to the latest version using brew update && brew upgrade --cask docker.
Description
Some versions of Docker Desktop might fail to start or function with the following error message:
Important
Those warnings are inaccurate. Docker Desktop is not affected by malware!
The reason for this warning is that some files in existing installations are incorrectly signed. This can be fixed by copying correctly signed files from the
Docker.appapplication bundle.Patch Releases
Tip
There are now patch releases for Docker Desktop versions
4.32to4.37available. Please refer to https://docs.docker.com/desktop/cert-revoke-solution/ for more detail.Workaround
Diagnose your Docker Desktop installation
To determine if you need to re-download and re-install Docker Desktop, please run the following steps.
check.sh.txtfile, rename it tocheck.shand set the executable flag withchmod +x check.sh. (Caution: it is never a good idea to just run shell scripts downloaded from the internet. Please take a moment to review the script before executing it.)Docker.appapplication bundle. The script will exit with0if the certificate was correctly verified:/Library/PrivilegedHelperToolsfolder with:./check.sh /Library/PrivilegedHelperTools/com.docker.vmnetdandsudo ./check.sh /Library/PrivilegedHelperTools/com.docker.socketPrivileged users
Tip
If you face this issue, try the following procedure (requires
rootuser access):If that still doesn't work, download one of the currently supported release from the Release notes, re-install the application and then finally re-apply step 2.
Non-privileged users
If the above instructions can't be used because you don't have
rootprivileges 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.Homebrew users
If you’ve installed Docker Desktop with Homebrew, you can update it to the latest version using
brew update && brew upgrade --cask docker.オリジナルは @cdupuis が docker/for-mac#7527 にポスト