Hello everyone, Borja from Docker here. First of all, I want to apologize for any issues you may be experiencing, and I’d like to invite all of you having such problems to please reach out to our customer support for help troubleshooting these situations.
As you may all know an overlay network isn’t a trivial piece of technology. When it comes to networking, it’s always been our goal to give our users the simplest and most performant, out of the box experience that works for all your networking needs.
The reality is that since we introduced 1.11 to nodes we’ve seen an increase in DNS lookup latency. Having said that, networking performance has not been affected. Weave running in user-space makes the overlay network performance to be dependant on CPU resources, as such it may be slow at times, or possibly break if there aren’t enough CPU resources available in the host. Today, Docker Cloud runs weave in user-space mode on any insecure private network, namely anywhere but AWS.
With the introduction of Docker 1.12 the networking stack in Docker is now able to satisfy the requirements of Docker Cloud. We have began work to switch to Docker 1.12 embedded DNS and swarm overlay network driver and rely on its performance and robustness for our user’s applications and networking.
We plan to provide more insight about this in a future post. Please continue to raise issues as you face them, and work with our support team to troubleshoot them. Your concerns are not going unheard and the team is working hard to provide you with the simplest and most performant way to run Docker in the cloud. Thank you!