docker build very slow unless you disconnect from the network. #1629
Comments
|
@djs55 This looks like related to IPV6 support, have you already seen this kind of problem : docker build performing lots of DNS lookups and thus being very slow ? |
|
It's hard to tell without looking at the logs and DNS packet trace in detail. I'll put this on my list of things to look at. |
|
Let me know if you want me to run any experiments? |
|
Let me know if you want me to use Wireshark to capture anything... and what in particular you need me to capture! Cheers! |
|
@djs55 What would you like me to capture to help with this? Building anything with the network up is painful in the extreme... |
|
@BrendonW sorry for the delay in replying. I took a look at the latest diagnostic upload and the DNS requests and responses look ok (all look fast, no delays) but there is a possibility that the successful IPv6 lookup is causing a problem because the Docker VM does not (yet) have fully working IPv6. I'll prepare an experimental patch which disables IPv6 lookups just in case they're causing a problem. |
Currently we don't have a working IPv6 stack so clients can't really use the IPv6 addresses they discover. They may cause confusion and possible request timeouts. This is an experiment to see if a network timeout bug is fixed in an IPv6 environment. Possibly related to [docker/for-mac#1629] Signed-off-by: David Scott <dave.scott@docker.com>
|
Attached is an experimental build of the networking component which disables IPv6 DNS lookups. To try it, download the attached vpnkit.zip, then:
If the problem still reproduces, could you trigger another diagnostic upload? Also would you be able to share a (perhaps cut down) |
|
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
|
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Expected behavior
docker build to be reasonably quick. Especially when all steps are in the cache.
Actual behavior
With network connection:
Information
Diagnostic ID: 07DC8946-60D1-4612-8928-A3F0082F575E
I suspect this MAY be related to IPv6...
but it really looks like a DNS issue:
As far as I can see, it is doing a ton of DNS lookups, almost all of which are not needed.
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: