docker
My mac OS always spam popup alert: "Docker.app" is damaged and can't be opened. You should move it to the trash
Description
I've just upgraded my Mac OS to Sequoia 15.3.1 and suddenly I got a popup alert as a subject. I was trying to remove that popup by reinstalling my docker, I downloaded docker with "Docker Desktop Apple Silicon", but in the end, I got another problem "Incompatible CPU detected" and this is Diagnostics ID: 14C08C03-C2C7-41C0-AE15-B8BB6178DC95/20250217035127
Could you help me please? This is my mac OS description:
Macbook Pro 13-inch, M1 2020 Chip: Apple M1 Memory: 8GB macOS: Sequoia 15.3.1
Warm Regards, Dimas
Reproduce
-
Download Docker Desktop Silicon Apple from the official website and this is the link: https://desktop.docker.com/mac/main/arm64/Docker.dmg?utm_source=docker&utm_medium=webreferral&utm_campaign=dd-smartbutton&utm_location=module&_gl=110d1or9_gcl_auMTEyMzc4MzczMy4xNzM5NzA0NzQ0_gaMTY3NzU3NjQxNS4xNzM5NzA0NzQ0_ga_XJWPQMJYHQ*MTczOTc2NDMyNS4yLjEuMTczOTc2NTEzNS41OC4wLjA.
-
Run dmg file
-
Copy Docker app to Applications
-
Try to run Docker App
-
The find show the pop up:
Expected behavior
-
Download Docker Desktop Silicon Apple from the official website and this is the link: https://desktop.docker.com/mac/main/arm64/Docker.dmg?utm_source=docker&utm_medium=webreferral&utm_campaign=dd-smartbutton&utm_location=module&_gl=110d1or9_gcl_auMTEyMzc4MzczMy4xNzM5NzA0NzQ0_gaMTY3NzU3NjQxNS4xNzM5NzA0NzQ0_ga_XJWPQMJYHQ*MTczOTc2NDMyNS4yLjEuMTczOTc2NTEzNS41OC4wLjA.
-
Run dmg file
-
Copy Docker app to Applications
-
Try to run Docker App
-
Docker App is running and this popup was gone:
docker version
Client:
Version: 27.5.1
API version: 1.47
Go version: go1.22.11
Git commit: 9f9e405
Built: Wed Jan 22 13:37:19 2025
OS/Arch: darwin/amd64 (rosetta)
Context: desktop-linux
Cannot connect to the Docker daemon at unix:///Users/macbookpro/.docker/run/docker.sock. Is the docker daemon running?
docker info
Client:
Version: 27.5.1
Context: desktop-linux
Debug Mode: false
Plugins:
ai: Ask Gordon - Docker Agent (Docker Inc.)
Version: v0.7.3
Path: /Users/macbookpro/.docker/cli-plugins/docker-ai
buildx: Docker Buildx (Docker Inc.)
Version: v0.20.1-desktop.2
Path: /Users/macbookpro/.docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.32.4-desktop.1
Path: /Users/macbookpro/.docker/cli-plugins/docker-compose
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.38
Path: /Users/macbookpro/.docker/cli-plugins/docker-debug
desktop: Docker Desktop commands (Beta) (Docker Inc.)
Version: v0.1.4
Path: /Users/macbookpro/.docker/cli-plugins/docker-desktop
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: /Users/macbookpro/.docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.27
Path: /Users/macbookpro/.docker/cli-plugins/docker-extension
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.5
Path: /Users/macbookpro/.docker/cli-plugins/docker-feedback
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.4.0
Path: /Users/macbookpro/.docker/cli-plugins/docker-init
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: /Users/macbookpro/.docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.16.1
Path: /Users/macbookpro/.docker/cli-plugins/docker-scout
Server:
ERROR: Cannot connect to the Docker daemon at unix:///Users/macbookpro/.docker/run/docker.sock. Is the docker daemon running?
errors pretty printing info
Diagnostics ID
14C08C03-C2C7-41C0-AE15-B8BB6178DC95/20250217035127
Additional Info
No response
Hi, I'm having a similar issue of Docker desktop showing a never-ending loop alert popup that "Docker" will damage my computer. I've trashed and re-installed the application multiple times, downloading the DMG from Docker's site for an Apple Silicon Chip.
I have:
Mac Book Pro 14-inch, 2021 Apple M1 Pro Memory: 16GB macOS: Sonoma 14.2
I have followed the same steps that @marcopolooo mentions above to install the application from dmg. However, I don't see the Incompatible CPU detected, but as soon as I copy the Docker app to the applications folder I see the malware popup and there's no way for it to go away aside from trashing the app. Pressing "Cancel" will have it reappear in about 2 minutes.
I've also followed steps to troubleshoot outlined in #7527. Here is the output from the check.sh script:
./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
Please let me know if you have any suggestions for how to troubleshoot further, or if there is a fix coming soon that might address this.
Thanks!
I had exactly the same problem when using the DMG file linked in the CTA button on the docker.com landing page. After logging on to app.docker.com I noticed another download link. After downloading it from there, I could install Docker Desktop without any problems. Verified that the checksums were identical on the DMG that worked.
(I'd comment on the above-linked bug, #7527, to which I was just referred by Docker support, but that bug is closed for comments...)
I've been having this problem for several months now on my 2024 Mac Studio (M2 Ultra) running MacOS 14.6.1.
The suggested fixes/workarounds, mentioned in #7527 and in various release notes, haven't helped.
In particular, the bug mentions a tiny shell script, check.sh, which just checks that the given binary is signed and has one of a specific pair of serial numbers, which seemingly are no longer accurate/valid.
As a result, when I downloaded the script and ran it against binaries from a freshly-downloaded (but not actually installed, since that immediately triggers the malware alerts) v4.43.2 Docker.app, the check fails:
$ ./check-docker.sh /Volumes/Docker/Docker.app/Contents/Library/LaunchServices/com.docker.vmnetd
-----------------------------------------------------------------
Certificate details for com.docker.vmnetd:
serial=42F679891BE44A8C
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=Apr 22 11:56:04 2025 GMT
notAfter=Feb 1 22:12:15 2027 GMT
-----------------------------------------------------------------
com.docker.vmnetd is signed with an unknown certificate
please download and install a new version of Docker Desktop
$
In fact, it looks like all of the files in the distribution/image are signed identically (not just "vmnetd"), so all of the binaries I tested fail the check.
Does that script just need updating?
AFAICT, this problem is definitely not resolved.
Chiming in to say I'm getting this every few weeks and it's incredibly annoying - I have to force quit, move to trash, re-download, reinstall. Is there any progress on this issue?
Docker tech support reached out to me, and gave me the script below, totalremovalDDmac.sh, to clean out a few more hard-to-reach spots in the system.
Their advice was to uninstall Docker, throw any existing installer in the trash and empty it, run the cleanup script, and finally download a fresh installer and run it.
After that, Docker Desktop worked fine for me. No more nags about corruption, and it's been a few weeks now, and I've been using Docker almost daily.
#!/bin/bash
# BRUTE FORCE Docker Desktop Kill Script
echo "KILLING ALL DOCKER PROCESSES..."
sudo pkill -f "Docker Desktop"
sudo pkill -f "com.docker"
sudo pkill -f "docker"
echo "FORCE STOPPING DOCKER SERVICES..."
sudo launchctl bootout system/com.docker.vmnetd 2>/dev/null
sudo launchctl bootout system/com.docker.socket 2>/dev/null
sudo launchctl remove com.docker.vmnetd 2>/dev/null
sudo launchctl remove com.docker.socket 2>/dev/null
echo "REMOVING DOCKER FILES..."
sudo rm -rf /Applications/Docker.app
sudo rm -rf /Library/PrivilegedHelperTools/com.docker.vmnetd
sudo rm -rf /Library/PrivilegedHelperTools/com.docker.socket
sudo rm -f /Library/LaunchDaemons/com.docker.vmnetd.plist
sudo rm -f /Library/LaunchDaemons/com.docker.socket.plist
sudo rm -f /var/run/com.docker.vmnetd.sock
echo "KILLING CONTAINER PROCESSES..."
sudo pkill -f "containerd"
sudo pkill -f "runc"
echo "REMOVING USER DATA (FORCE)..."
sudo rm -rf ~/Library/Containers/com.docker.docker
sudo rm -rf ~/Library/Group\ Containers/group.com.docker
sudo rm -rf ~/.docker
echo "CLEANING UP ANY REMAINING PROCESSES..."
sudo pkill -f "Docker"
sudo pkill -f "docker"
echo "Docker Desktop COMPLETELY KILLED"