# 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:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mmatos](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@Mmatos](https://discuss.elastic.co/u/Mmatos)\
**Post date:** [December 1, 2021, 6:24pm UTC](https://discuss.elastic.co/t/elasticsearch-node-running-on-docker-only-shows-disk-available-50-gb/290704/1 "2021-12-01T18:24:33Z")

</div>

Hi,  
I am running the Docker-Elk Stack 7.14.1 and noticed that in the Stack Monitoring Tab Elastic reports it only has a 50 GB disk.  
The host running the container has 700 GB free. How can I expand this container so it can use all the available free space on the host?

Because of the size limitation, the disk fills up in days that is a problem because I can not store more data even with the free space available.

At the moment I am using the default docker-compose file with the volumes assigned. The data persist but is limited to 50 GB.

![image](https://us1.discourse-cdn.com/elastic/original/3X/4/2/4290b7be18346e00053cb82234606cd6e1803624.png)

---

<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…

---

<div class="post-metadata">

**Author:** ![rcowart](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rcowart/32/88091_2.png) [@rcowart](https://discuss.elastic.co/u/rcowart)\
**Post date:** [December 1, 2021, 8:22pm UTC](https://discuss.elastic.co/t/elasticsearch-node-running-on-docker-only-shows-disk-available-50-gb/290704/3 "2021-12-01T20:22:25Z")

</div>

@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:

```auto
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)...

```nohighlight
    volumes:
      - /mnt/data0/elasticsearch:/usr/share/elasticsearch/data
      - /etc/certs:/usr/share/elasticsearch/config/certificates

```

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 29, 2021, 8:22pm UTC](https://discuss.elastic.co/t/elasticsearch-node-running-on-docker-only-shows-disk-available-50-gb/290704/4 "2021-12-29T20:22:45Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.