# Es7 cluster problem with docker-compose

**URL:** <https://discuss.elastic.co/t/es7-cluster-problem-with-docker-compose/214002>\
**Category:** Elasticsearch\
**Tags:** docker, ccs-cross-cluster-search\
**Created:** [January 7, 2020, 8:04am UTC](https://discuss.elastic.co/t/es7-cluster-problem-with-docker-compose/214002 "2020-01-07T08:04:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nathan-zhu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathan-zhu/32/60334_2.png) [@nathan-zhu](https://discuss.elastic.co/u/nathan-zhu)\
**Post date:** [January 7, 2020, 8:04am UTC](https://discuss.elastic.co/t/es7-cluster-problem-with-docker-compose/214002/1 "2020-01-07T08:04:27Z")

</div>

Hi, i use es7.5.1 latest version. try to use docker-compose to build cluster service, plan to have three nodes and two master. and use kibana to manager it.  
here is docker-compose.yml file

```
version: '2.2'
services:
  es01:
    image: docker.elastic.co/elasticsearch/elasticsearch:7.5.1
    container_name: es01
    environment:
      - node.name=es01
      - cluster.name=es-docker-cluster
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
      - discovery.seed_hosts=es01,es02,es03
      - cluster.initial_master_nodes=es01,es02,es03
    ulimits:
      memlock:
        soft: -1
        hard: -1
    volumes:
      - data01:/data1/elasticsearch/es7/data
    ports:
     - 9201:9200
    networks:
      - elastic

  es02:
    image: docker.elastic.co/elasticsearch/elasticsearch:7.5.1
    container_name: es02
    environment:
      - node.name=es02
      - cluster.name=es-docker-cluster
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
      - discovery.seed_hosts=es01,es02,es03
      - cluster.initial_master_nodes=es01,es02,es03
    ulimits:
      memlock:
        soft: -1
        hard: -1
    volumes:
      - data02:/data1/elasticsearch/es7/data
    ports:
      - 9202:9200
    networks:
      - elastic
  es03:
    image: docker.elastic.co/elasticsearch/elasticsearch:7.5.1
    container_name: es03
    environment:
      - node.name=es03
      - cluster.name=es-docker-cluster
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
      - discovery.seed_hosts=es01,es02,es03
      - cluster.initial_master_nodes=es01,es02,es03
    ulimits:
      memlock:
        soft: -1
        hard: -1
    volumes:
      - data03:/data1/elasticsearch/es7/data
    ports:
      - 9203:9200
    networks:
      - elastic

  kibana:
    image: docker.elastic.co/elasticsearch/elasticsearch:7.5.1
    container_name: kibana75
    environment:
      SERVER_NAME: kibana
      ELASTICSEARCH_HOSTS: ["http://es01:9201", "http://es02:9202","http://es03:9203"]
    ports:
      - 5601:5601
    networks:
      - elastic

volumes:
  data01:
    driver: local
  data02:
    driver: local
  data03:
    driver: local

networks:
  elastic:
    driver: bridge

```

after start docker-compose get nodes working well;  
`curl http://localhost:9202/_cat/nodes?v`

> ip heap.percent ram.percent cpu load\_1m load\_5m load\_15m node.role master name  
> 192.168.112.2 23 43 4 1.54 1.09 0.57 dilm - es01  
> 192.168.112.4 40 43 2 1.54 1.09 0.57 dilm - es03  
> 192.168.112.5 27 43 2 1.54 1.09 0.57 dilm \* es02

but kibana can't connect to elasticsearch server, where is problem, can help on it? thanks.

get error info at below:

> ERROR: [1] bootstrap checks failed  
> [1]: the default discovery settings are unsuitable for production use; at least one of [discovery.seed\_hosts, discovery.seed\_providers, cluster.initial\_master\_nodes] must be configured

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 4, 2020, 8:04am UTC](https://discuss.elastic.co/t/es7-cluster-problem-with-docker-compose/214002/2 "2020-02-04T08:04:37Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.