Elastic Search Docker Container Throwing a Ton of unexpected error while indexing monitoring document exceptions

[kevinjcoleman (Kevin Coleman)]

We're using the docker container with docker-compose, here's our configuration. Is there something I'm missing here?

  ln_elasticsearch:
    image: docker.elastic.co/elasticsearch/elasticsearch:6.2.1
    container_name: ln_elasticsearch
    environment:
      - discovery.type=single-node
    volumes:
      - esdata1:/usr/share/elasticsearch/data
    ports:
      - 9200:9200

ln_elasticsearch    | [2018-02-08T21:34:51,958][WARN ][o.e.x.m.e.l.LocalExporter] unexpected error while indexing monitoring document
ln_elasticsearch    | org.elasticsearch.xpack.monitoring.exporter.ExportException: ClusterBlockException[blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];]
ln_elasticsearch    | 	at org.elasticsearch.xpack.monitoring.exporter.local.LocalBulk.lambda$throwExportException$2(LocalBulk.java:140) ~[?:?]
...
ln_elasticsearch    | flood stage disk watermark [95%] exceeded on [mFL5ilQRQmu8TuOx0pg1rw][mFL5ilQ][/usr/share/elasticsearch/data/nodes/0] free: 32.2mb[0%], all indices on this node will marked read-only

[dadoonet (David Pilato)]

You don't have enough disk space available.
If it's not for production, then you can add the following to your environment:

- cluster.routing.allocation.disk.threshold_enabled=false

But 32.2mb sounds very low free disk space...

[kevinjcoleman (Kevin Coleman)]

Thanks that's helpful! Can you think of a reason why the container would be running out of space like that?

[dadoonet (David Pilato)]

Nope. I guess it's a Docker configuration issue may be?