Reminds me when I wrote this script to solve Docker's weird thing it does with virtualization on macOS sometimes. You need to completely remove anything Docker ,reinstall it, then shuffle some files around.

```

brew remove docker

brew remove docker-compose

brew remove docker-completion

brew remove docker-buildx

brew remove --cask docker

brew install --cask docker --force

sudo pkill '[dD]ocker'

sudo launchctl bootout system /Library/LaunchDaemons/com.docker.vmnetd.plist

sudo launchctl bootout system /Library/LaunchDaemons/com.docker.socket.plist

sudo rm -f /Library/PrivilegedHelperTools/com.docker.vmnetd

sudo rm -f /Library/PrivilegedHelperTools/com.docker.socket

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/

```

Missing from the title is the fact that this happened in early January.

I thought it referred to a repeat incident, but no, it's the same one that has long been fixed.

When you want vendor lockin docker seems counter productive.