5 ms·

The company claimed back in March [0] that Docker for Mac addresses the filesystem events. I observed that it works. While Docker for Mac has improved somewhat

by gkop 10y ago

The company claimed back in March [0] that Docker for Mac addresses the filesystem events. I observed that it works. While Docker for Mac has improved somewhat over the beta, unfortunately it's still quite rough. For example, it was only last week that they pushed a fix for the DNS timeout issue [1] (I think maybe it was fixed? I can't check because Docker for Mac is not open source). [0] https://blog.docker.com/2016/03/docker-for-mac-windows-beta/ https://blog.docker.com/2016/03/docker-for-mac-windows-beta/ [1] https://forums.docker.com/t/intermittent-dns-resolving-issues/9584 https://forums.docker.com/t/intermittent-dns-resolving-issue...

djs55 10y ago
The DNS resolving code in Docker for Mac is in the VPNkit project which is open-source: https://github.com/docker/vpnkit https://github.com/docker/vpnkit. A DNS timeout is a fairly general symptom and it's hard to diagnose fully without a packet capture, but there's one issue that I'm aware of: if the primary server is down then the UDP DNS queries and responses will use the host's second server. However if a response is large and requires TCP then unfortunately we will still forward it to the primary server, which obviously won't work :( I've filed this issue about it: https://github.com/docker/vpnkit/issues/96 https://github.com/docker/vpnkit/issues/96. We hope to improve DNS, VPN and general proxy support for 1.13 -- please do file issues for any other bugs you find!