Error: One or more processes are already bound to port 53: mDNSResponder

Zero Trust
1

Posting this here since the original thread was prematurely closed.

After upgrading docker desktop on mac to 4.24.x, I was getting this error when starting warp on MacOS:

The WARP agent must be the only process responsible for DNS resolution on this device. One or more processes are already bound to port 53: mDNSResponder

The solution seems to be:

  • Edit ~/Library/Group\ Containers/group.com.docker/settings.json and set “kernelForUDP” to false
  • Restart Docker Desktop

https://github.com/docker/for-mac/issues/7008#issuecomment-1746653802
https://docs.docker.com/desktop/release-notes/#for-mac-3
https://community.cloudflare.com/t/zerotrust-unable-to-connect-port-53-bound/486081

4 Likes
3

Worked for me

4

It worked for me too!
Thanks!

5

I just spend whole week trying to figure this issue out, since I’m not using Docker Desktop.
I’m using Podman Desktop and it wasn’t the problem…

Apparently I installed minikube in QEMU, and this installation needed socket_vmnet! And this driver caused mDNSResponder to bind on :53!

So for future reference, if it’s not Docker, it might be socket_vmnet (installed via brew in my case)