Mac 启动docke报错 com.docker.vmnetd【解决方案】

2025/1/11 21:02:55 来源：https://blog.csdn.net/weixin_41104307/article/details/145065174 浏览: 次关键词：Mac 启动docke报错 com.docker.vmnetd【解决方案】

今天不知道 docker抽了啥疯，突然提示更新，更新完就报错

而且还无限的提示，下载最新的版本，更新还是不行---

于是google查了一下，噢噢噢噢，果然有问题

issiue如下

Malware detection prevents Docker Desktop to start #7527

解决方案

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.

Patch Releases

Tip

There are now patch releases for Docker Desktop versions 4.32 to 4.37 available. Please refer to Fix startup issue for Mac | Docker Docs for more detail.

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

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.