# ILM not reclaiming back space in ELK Host server

**URL:** <https://discuss.elastic.co/t/ilm-not-reclaiming-back-space-in-elk-host-server/290218>\
**Category:** Elastic Observability\
**Tags:** ilm-index-lifecycle-management\
**Created:** [November 25, 2021, 9:03pm UTC](https://discuss.elastic.co/t/ilm-not-reclaiming-back-space-in-elk-host-server/290218 "2021-11-25T21:03:27Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [December 1, 2021, 5:25pm UTC](https://discuss.elastic.co/t/ilm-not-reclaiming-back-space-in-elk-host-server/290218/12 "2021-12-01T17:25:50Z")

</div>

Well That explains it.. you did not say you are running inside docker. 🙂

As you found out Docker manages the Docker container Volume size not Elasticsearch.

Also it is not best use the internal docker container volume for the elasticsearch data. best practice is to mount the elastic data path to a volume on the host.

See Here

> **[Install Elasticsearch with Docker | Elasticsearch Guide \[8.11\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html)**

> #### Always bind data volumes
> 
> You should use a volume bound on `/usr/share/elasticsearch/data` for the following reasons:
> 
> 1. The data of your Elasticsearch node won’t be lost if the container is killed
> 2. Elasticsearch is I/O sensitive and the Docker storage driver is not ideal for fast I/O
> 3. It allows the use of advanced [Docker volume plugins](https://docs.docker.com/engine/extend/plugins/#volume-plugins)

Example

```auto
    volumes:
      - data01:/usr/share/elasticsearch/data

```

Also look at some good advice here

> [@Elasticsearch Node Running on docker only shows Disk Available 50 GB](https://discuss.elastic.co/t/elasticsearch-node-running-on-docker-only-shows-disk-available-50-gb/290704/3):
>
> @stephenb is correct. The one thing I would add is that the Elasticsearch docker image will run as user ID and group ID 1000. So make sure that this user owns the path. For example: mkdir /mnt/data0/elasticsearch && chown -R 1000:1000 /mnt/data0/elasticsearch Then bind mount this path to the Elasticsearch container. The following example is from one of our docker compose files (you can also see how we mounted the path to certificates)... volumes: - /mnt/data0/elasticsearch:/usr/sha…

---

_[View the full topic](https://discuss.elastic.co/t/ilm-not-reclaiming-back-space-in-elk-host-server/290218)._