ElasticSearch Container got Killed

Build Environment
3

Hi @jaredrhine!

I appreciate very much your help!

I found one solution, for now. Limiting HEAP size of Elastic Search.

I found out that container got kille (exit code 137), because it was using much memory.

Follow our config.yml:

 - image: docker.elastic.co/elasticsearch/elasticsearch:5.6.2
        environment:
          - discovery.type=single-node
          - http.host=0.0.0.0
          - transport.host=127.0.0.1
          - xpack.security.enabled=false
          - ES_JAVA_OPTS=-Xms750m -Xmx750m

Thank you very much!

Source: https://github.com/10up/wp-local-docker/issues/6

1 Like