Share and learn in the Docker community.
Hi, I am trying to install docker for macbook m2 however every time the download completes and i try to install i receive the following error message, can anyone assist or provide a solution to this please?
Malware Blocked
“com.docker.vmnetd” was not opened because it contains malware. This action did not harm your Mac.
I’ve tried uninstalling then downloading and reinstalling everything nothing seems to work!
Do you have an antivirus installed on Mac? If you have, which one?
No, I haven’t installed any antivirus. Yesterday, I had used docker. Today again, when I tried to open it, it showed this error so I deleted it and then reinstalled it again but the same error reappeared!
Hey, I am getting similar warning just today
“com.docker.socket” was not opened because it contains malware. this action did not harm your mac.
I donot have any antivirus, this is warning from builtin apple
I’ve been using Docker Desktop on my Mac for months and today, an error message suddenly popped up : “Malware blocked … com.docker.vmnetd”. Not sure if it happened after a macOS update or a Docker update. As a result, I got a blank containers screen and Docker wouldn’t stop. I rebooted my Mac to find out the malware warning now pops up every 10 seconds and I can’t open Docker Desktop any more.
I uninstalled then reinstalled the Docker app with no results.
Following some advice, I then removed ~/.docker and /Library/LaunchDaemons/com.docker.*, uninstalled and reinstalled Docker. I still got the malware warning the first time I run it, but at least I could start Desktop and get my list of containers. It didn’t last long though, as the containers crashed and I got another error message.
Since then I haven’t been able to restart Desktop. It seems it was trying to repair vmnet when it crashed, possibly restoring com.docker.vmnetd.plist into /Library/LaunchDaemons, which is probably what sets macOS on a malware killing spree…
I’m not sure what to do now as I have the latest version of everything…
Thanks for your help
When did you first notice this error today? It is rare that people find the forum at the same time with the same issue, unless it just happened minutes ago with everyone.
I opened docker an hour ago and this error appeared.
just 20 minutes before, i searched for a while if its an existing issue on internet before getting to this link
I have been using docker for more than a year, all of sudden it has come now after a system reboot
Then let’s see what happens if I reboot my Mac, because I could stop and start my Desktop without a problem. I will be back soon.
update:
Rebooted and still no problem with Docker Desktop
I am getting identical errors. I do not have anti-malware software installed on Mac OS Sequoia 15.2, M1-Pro Apple Silicon
docker.app was automatically moved to trash.
Now I am getting the malware warning “com.docker.socket”.
Awaiting for the official word on how to eliminate these errors.
Did it happen to you also after rebooting the machine? Did you update anything on macOS or Docker Desktop itself before that?
Yes. When I reboot I still get the com.docker.socket error.
I have not used Docker Desktop in a couple of months. My macOS is up to date.
This started today when I started my computer. It started with the malware warning for “com.docker.vmnetd” . When I attempted to open the app, I got a message saying that the docker app was automatically moved to the Trash.
Note I am running on an Apple silicon M1 Pro
Im also facing same issue - “com.docker.vmnetd” was not opened because it contains malware. This action did not harm your Mac.
I was using an Apple M1 Air, and despite the warning, I am still able to run Docker unlike analyticarts which was moved to trash
(also I recently updated macOS a few days ago, but there was no warning till today)
Sorry, I was no clear enough. I tried to find out if the error happened first only after rebooting the machine, but you answered that too.
Just got the same error. Uninstalled and tried older versions of Docker and am getting the same error.
Running on MacOS Sequoia 15.2 and M2.
Could any of you create an issue on GitHub?
Since so many of you have this issue, please first share here that you are going to create an issue so everyone else can wait until you share the link to the existing issue. If all of you comment there, developers will see that and you can get official response faster.
I also managed to get a response from Docker in the meantime. They are investigating.
