gliderlabs
Docker image not respecting /etc/hosts
Has something changed recently with the docker image? I know that my consul-demo running progrium/docker used to work: however the latest tag is no longer finding linked containers
Under the old tag, this compose file https://github.com/micahhausler/consul-demo/blob/master/docker-compose.yml#L11-L33 worked, however the current latest tagged image doesn't look up the linked container IP in /etc/hosts.
We switched to Alpine because Busybox broke. However, I don't see any problems with linked containers or /etc/hosts ... can you validate it somehow? Also I don't recommend linked containers anyway. Try something like resolvable.
On Thu, Jul 9, 2015 at 7:00 PM, Micah Hausler [email protected] wrote:
Has something changed recently with the docker image? I know that my consul-demo running progrium/docker used to work: however the latest tag is no longer finding linked containers
Under the old tag, this compose file https://github.com/micahhausler/consul-demo/blob/master/docker-compose.yml#L11-L33 worked, however the current latest tagged image doesn't look up the linked container IP in /etc/hosts.
— Reply to this email directly or view it on GitHub https://github.com/gliderlabs/docker-consul/issues/96.
Jeff Lindsay http://progrium.com
I am seeing the same thing, even trying the newer gliderlabs/consul* images. I've recently switched to using docker-machine (with boot2docker) instead of boot2docker directly, perhaps that or a newer Docker version could be the culprit?
