# Elasticsearch Node Running on docker only shows Disk Available 50 GB

**URL:** https://discuss.elastic.co/t/elasticsearch-node-running-on-docker-only-shows-disk-available-50-gb/290704
**Category:** Elasticsearch
**Tags:** docker
**Created:** [December 1, 2021, 6:24pm UTC](https://discuss.elastic.co/t/elasticsearch-node-running-on-docker-only-shows-disk-available-50-gb/290704 "2021-12-01T18:24:33Z")
**Posts on this page:** 1
**Showing post:** 2

<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, 7:53pm UTC](https://discuss.elastic.co/t/elasticsearch-node-running-on-docker-only-shows-disk-available-50-gb/290704/2 "2021-12-01T19:53:48Z")

</div>

See Here :

You are seeing the size of the Docker Volume.

> [@ILM not reclaiming back space in ELK Host server](https://discuss.elastic.co/t/ilm-not-reclaiming-back-space-in-elk-host-server/290218/12):
>
> Well That explains it.. you did not say you are running inside docker. slight_smile 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 Always bind data volumes You should use a volume bound on /usr/share/elasticsearch/data for the following reasons: The data of your Elasticsearch nod…

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-node-running-on-docker-only-shows-disk-available-50-gb/290704)._