Stopped working in docker desktop for mac v2.1.0.0 about docker-dnsmasq

[andyshinn]

We'll probably need to gather some more information to troubleshoot. Maybe we can start by checkout out what is running on the VM ports? Maybe the new Docker for Mac is running DNS on the host VM?

Also, can you clarify some things:

• The IP addresses of Consul container and dnsmasq?
• Is 172.20.20.1 the Consul container and it is listening on both 53 and 8600 somehow?
• Are you querying from another container? If so, how was it run?

If you can provide some example config and run commands for Consul I can try it out locally. I haven't upgraded to the edge release yet but I can do so to test if I have a reproduction scenario.

[benschw]

Looks like this is a docker for mac issue blocking UDP ports under 1024:

docker/for-mac#3775

Sorry for the distraction, and thanks for the quick response!

[andyshinn]

No worries, thanks for linking to the upstream so others finding this issue can follow the root cause.