Following the instructions at https://www.elastic.co/guide/en/elastic-stack-get-started/current/get-started-docker.html does not lead to a success!
As this is a local test environment I made absolutely no changes to the docker-compose.yml file.
However, I see those errors:
> es01 | {"type": "server", "timestamp": "2020-03-31T13:35:13,566Z", "level": "WARN", "component": "o.e.c.c.ClusterFormationFailureHelper", "cluster.name": "es-docker-cluster", "node.name": "es01", "message": "master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes [es01, es02, es03] to bootstrap a cluster: have discovered [{es01}{dMtytnb9RlivJhX5gCbEbw}{piAw7ov4RPWXtl5txTYPjQ}{172.22.0.5}{172.22.0.5:9300}{dilm}{ml.machine_memory=8335745024, xpack.installed=true, ml.max_open_jobs=20}]; discovery will continue using [172.22.0.3:9300, 172.22.0.2:9300] from hosts providers and [{es01}{dMtytnb9RlivJhX5gCbEbw}{piAw7ov4RPWXtl5txTYPjQ}{172.22.0.5}{172.22.0.5:9300}{dilm}{ml.machine_memory=8335745024, xpack.installed=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0" }
> es02 | {"type": "server", "timestamp": "2020-03-31T13:35:13,654Z", "level": "WARN", "component": "o.e.c.c.ClusterFormationFailureHelper", "cluster.name": "es-docker-cluster", "node.name": "es02", "message": "master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes [es01, es02, es03] to bootstrap a cluster: have discovered [{es02}{8fH1nye2RGyKKO7HXBCwRQ}{2agenrE1QKGWwNboiWJ1LA}{172.22.0.3}{172.22.0.3:9300}{dilm}{ml.machine_memory=8335745024, xpack.installed=true, ml.max_open_jobs=20}]; discovery will continue using [172.22.0.5:9300, 172.22.0.2:9300] from hosts providers and [{es02}{8fH1nye2RGyKKO7HXBCwRQ}{2agenrE1QKGWwNboiWJ1LA}{172.22.0.3}{172.22.0.3:9300}{dilm}{ml.machine_memory=8335745024, xpack.installed=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0" }
> es03 | {"type": "server", "timestamp": "2020-03-31T13:35:21,707Z", "level": "WARN", "component": "o.e.c.c.ClusterFormationFailureHelper", "cluster.name": "es-docker-cluster", "node.name": "es03", "message": "master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes [es01, es02, es03] to bootstrap a cluster: have discovered [{es03}{J3s-ulDcRhqbYT8dmMav9w}{uHscQSXLQve2tJLLBvdDDA}{172.22.0.2}{172.22.0.2:9300}{dilm}{ml.machine_memory=8335745024, xpack.installed=true, ml.max_open_jobs=20}]; discovery will continue using [172.22.0.5:9300, 172.22.0.3:9300] from hosts providers and [{es03}{J3s-ulDcRhqbYT8dmMav9w}{uHscQSXLQve2tJLLBvdDDA}{172.22.0.2}{172.22.0.2:9300}{dilm}{ml.machine_memory=8335745024, xpack.installed=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0" }
Logging into the containers, I'm able to ping each of them. DNS works.
Re-creating the network does not solve the problem.
I'm running
Docker version 19.03.8, build afacb8b
docker-compose version 1.25.0, build 0a186604