Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Servers, nginx and Docker

macOS says Docker.app is damaged or will harm your Mac

ErrorDocker.app is damaged and can't be opened

Short answer

Two different things hide behind this warning. A drag-and-drop install that was interrupted leaves a half-copied app that Gatekeeper calls damaged. Some older Docker Desktop installs also had wrongly signed helper files that triggered a malware dialog. Reinstall for the first, update Docker Desktop for the second.

  • Applies to Docker Desktop 4.x for Mac, macOS 14 and 15
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Read the dialog text and check the Docker Desktop version. 'Damaged' points to the first cause; a malware dialog naming a Docker helper points to the second.

    defaults read /Applications/Docker.app/Contents/Info.plist CFBundleShortVersionString
  2. 2Match what you see, then jump to its fix

    1. 1Docker.app is damaged and can't be opened, often right after an install or an update from a DMGA drag-and-drop install was interrupted and left a partial copyFix
    2. 2A malware dialog names a Docker helper (com.docker.vmnetd or com.docker.socket) and says the action did not harm your MacAn older Docker Desktop install has a wrongly signed helper fileFix

What does the error look like?

  • Docker.app is damaged and can't be opened
  • A malware or 'will damage your computer' dialog naming a Docker helper such as com.docker.vmnetd
  • This action did not harm your Mac.

Cause 1 of 2

A drag-and-drop install was interrupted and left a partial copy

1Check

Copying from a DMG is not atomic. If another program such as an editor or terminal calls the Docker CLI during the copy, the app can end up half copied, and Gatekeeper marks it damaged.

ls -ld /Applications/Docker.app
pgrep -fl docker

2Fix

Quit every program that calls Docker (editors, terminals, scripts). Move /Applications/Docker.app to the Trash and empty it. Eject the DMG and mount it again, then reinstall.

mv /Applications/Docker.app ~/.Trash/
# empty the Trash, eject and re-mount the DMG, then drag Docker in again

3Verify

Docker Desktop opens and the CLI answers.

open -a Docker
docker version

Confirmed by docs.docker.com

Did this fix it?

Cause 2 of 2

An older Docker Desktop install has a wrongly signed helper file

1Check

Docker's own statement is that these warnings are inaccurate and Docker Desktop is not affected by malware; some files in existing installations were incorrectly signed. Patch releases exist for 4.32 to 4.37, and the fix is in current releases. Compare your version with the latest.

defaults read /Applications/Docker.app/Contents/Info.plist CFBundleShortVersionString
ls -l /Library/PrivilegedHelperTools/ | grep docker

2Fix

Update Docker Desktop to the current release (in the app, or with Homebrew if that is how it was installed). Do not disable Gatekeeper.

brew update && brew upgrade --cask docker

3Verify

Start Docker Desktop and confirm the dialog no longer appears.

open -a Docker && docker version

Confirmed by github.com

Did this fix it?

How do I stop it coming back?

  • Quit editors, terminals and scripts that call Docker before installing from a DMG, and keep the DMG mounted until the copy finishes.
  • In managed environments use the PKG installer instead of drag-and-drop.
  • Update Docker Desktop from inside the app instead of copying a new Docker.app over the old one.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.