# Cannot start elasticsearch from Docker

**URL:** <https://discuss.elastic.co/t/cannot-start-elasticsearch-from-docker/193853>\
**Category:** Elasticsearch\
**Created:** [August 5, 2019, 5:22pm UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-from-docker/193853 "2019-08-05T17:22:59Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tomsk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tomsk/32/22061_2.png) [@tomsk](https://discuss.elastic.co/u/tomsk)\
**Post date:** [August 5, 2019, 5:23pm UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-from-docker/193853/1 "2019-08-05T17:23:00Z")

</div>

Hello, I want to install elasticsearch using Docker, this is in `docker-compose.yml`:

```
version: '2'
services:
  elasticsearch:
    image: docker.elastic.co/elasticsearch/elasticsearch:5.6.16
    container_name: elasticsearch
    restart: unless-stopped
    environment:
      - network.host=127.0.0.1
      - http.port=9200
      - cluster.name=elasticsearch
      - node.name="db-master"
      - node.master=true
      - node.data=true
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms2g -Xmx2g"
    ulimits:
      memlock:
        soft: -1
        hard: -1
    mem_limit: 2g
    volumes:
      - esdata:/usr/share/elasticsearch/data
    ports:
      - 9200:9200
    networks:
      - esnet

volumes:
  esdata:
    driver: local

networks:
  esnet:

```

After `docker-compose up` I will get:

```
elasticsearch is up-to-date
Attaching to elasticsearch
elasticsearch exited with code 137

```

There is 4GB RAM on the server.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 5, 2019, 5:33pm UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-from-docker/193853/2 "2019-08-05T17:33:17Z")

</div>

Your heap size should be 50% of available RAM. Here you have set both to 2GB which will not work.

---

<div class="post-metadata">

**Author:** ![tomsk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tomsk/32/22061_2.png) [@tomsk](https://discuss.elastic.co/u/tomsk)\
**Post date:** [August 5, 2019, 6:09pm UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-from-docker/193853/3 "2019-08-05T18:09:28Z")

</div>

So it means that elasticsearch can use only 50% of available RAM? What to do with another 50%? Because it is wasted then.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 5, 2019, 6:11pm UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-from-docker/193853/4 "2019-08-05T18:11:15Z")

</div>

Elasticsearch uses both heap and off-heap RAM, e.g. for the operating system file cache, so all available memory is usually used.

---

<div class="post-metadata">

**Author:** ![tomsk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tomsk/32/22061_2.png) [@tomsk](https://discuss.elastic.co/u/tomsk)\
**Post date:** [August 5, 2019, 6:12pm UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-from-docker/193853/5 "2019-08-05T18:12:27Z")

</div>

Ah okey, so it started and one more question, elastic started on port 9300, why? I set it to be on 9200.

---

<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:** [September 4, 2019, 9:22am UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-from-docker/193853/7 "2019-09-04T09:22:48Z")

</div>

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