News for hackers. Stuff that matters.
Re:Docker 1.10.0 is out by shykes on Thursday February 04, 2016 @11:00PM (#11039299)
Docker assumes it cannot trust the container's DNS resolver to respect TTL and cache in a compliant way. So it guarantees stable name->ip mapping for each container. As a result, when you point a service endpoint at another container, it's the IP/container mapping that is changed, which is a much more reliable and atomic change. I would definitely never rely on changing DNS records to orchestrate changes to my production stack, that would be way too brittle.
Re:Docker 1.10.0 is out by falcolas on Friday February 05, 2016 @09:05AM (#11041424)
The real problem is that you can't trust the program's resolver, either. Java will behave differently than Go, which behaves differently from Python, and so on.