Build custom images for ElasticSearch & Kibana
We can then remove X-Pack and control ElasticSearch's memory usage. This also gives us the opportunity to let Kibana do its optimization when we build the image, rather than every time the container is recreated.
This commit is contained in:
@@ -20,7 +20,7 @@ rabbit:
|
||||
ports:
|
||||
- "127.0.0.1:5672:5672"
|
||||
elastic:
|
||||
image: docker.elastic.co/elasticsearch/elasticsearch:5.6.1
|
||||
image: armadillica/elasticsearch:latest
|
||||
container_name: elastic
|
||||
restart: always
|
||||
volumes:
|
||||
@@ -28,10 +28,8 @@ elastic:
|
||||
- /data/storage/elastic:/usr/share/elasticsearch/data
|
||||
ports:
|
||||
- "127.0.0.1:9200:9200"
|
||||
environment:
|
||||
xpack.security.enabled: 'false'
|
||||
kibana:
|
||||
image: docker.elastic.co/kibana/kibana:5.6.1
|
||||
image: armadillica/kibana:latest
|
||||
container_name: kibana
|
||||
restart: always
|
||||
environment:
|
||||
|
Reference in New Issue
Block a user