I've been doing some experimentation and development with Elasticsearch and Kibana running in the official docker containers. I've got the ElasticSearch /usr/share/elasticsearch/data mapped to a 1.5TB drive which seems to be automatically maintaining the disk space to 95%.
However, for some reason my / drive (which also handles the /var/lib/docker/overlay2/ container storage) has filled up.
How can I figure out what inside the docker containers (either Kibana or Elasticsearch) is filling up my / drive? Should I relocate my default /var/lib/docker to the external /data drive?
My docker-compose configs are like this:
- name: Build Elasticsearch Docker Image
docker_service:
project_name: elasticsearch
definition:
version: '3'
services:
elasticsearch:
image: docker.elastic.co/elasticsearch/elasticsearch:{{ elastic_version }}
container_name: elasticsearch
restart_policy:
condition: on-failure
delay: 5s
max_attempts: 3
window: 120s
environment:
- bootstrap.memory_lock=true
- "ELASTIC_PASSWORD=changeme"
- "ES_JAVA_OPTS=-Xms16g -Xmx16g"
- xpack.security.enabled=false
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536
hard: 65536
volumes:
- /data/elasticsearch/data:/usr/share/elasticsearch/data
- /var/log/elasticsearch:/var/log/elasticsearch
ports:
- 9200:9200
networks: ['stack']
networks: {stack: {}}
- name: Build Kibana Docker Image
docker_service:
project_name: kibana
definition:
version: '3'
services:
kibana:
image: docker.elastic.co/kibana/kibana:{{ kibana_version }}
container_name: kibana
restart_policy:
condition: on-failure
delay: 5s
max_attempts: 3
window: 120s
environment:
- ELASTICSEARCH_URL=http://localhost:9200
ports:
- 5601:5601
networks: ['stack']
networks: {stack: {}}