Mac is detecting Docker as a malware and keeping it from starting

Reminds me when I wrote this script to solve Docker&#x27;s weird thing it does with virtualization on macOS sometimes. You need to completely remove anything Docker ,reinstall it, then shuffle some files around.<p>```<p>brew remove docker<p>brew remove docker-compose<p>brew remove docker-completion<p>brew remove docker-buildx<p>brew remove --cask docker<p>brew install --cask docker --force<p>sudo pkill &#x27;[dD]ocker&#x27;<p>sudo launchctl bootout system &#x2F;Library&#x2F;LaunchDaemons&#x2F;com.docker.vmnetd.plist<p>sudo launchctl bootout system &#x2F;Library&#x2F;LaunchDaemons&#x2F;com.docker.socket.plist<p>sudo rm -f &#x2F;Library&#x2F;PrivilegedHelperTools&#x2F;com.docker.vmnetd<p>sudo rm -f &#x2F;Library&#x2F;PrivilegedHelperTools&#x2F;com.docker.socket<p>sudo cp &#x2F;Applications&#x2F;Docker.app&#x2F;Contents&#x2F;Library&#x2F;LaunchServices&#x2F;com.docker.vmnetd &#x2F;Library&#x2F;PrivilegedHelperTools&#x2F;<p>sudo cp &#x2F;Applications&#x2F;Docker.app&#x2F;Contents&#x2F;MacOS&#x2F;com.docker.socket &#x2F;Library&#x2F;PrivilegedHelperTools&#x2F;<p>```

Missing from the title is the fact that this happened in early January.<p>I thought it referred to a repeat incident, but no, it&#x27;s the same one that has long been fixed.

When you want vendor lockin docker seems counter productive.