# Docker and disk size **URL:** \ **Category:** Elasticsearch\ **Created:** [December 28, 2017, 2:04pm UTC](https://discuss.elastic.co/t/docker-and-disk-size/113453 "2017-12-28T14:04:46Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![javadevmtl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javadevmtl/32/45613_2.png) [@javadevmtl](https://discuss.elastic.co/u/javadevmtl)\ **Post date:** [December 28, 2017, 2:04pm UTC](https://discuss.elastic.co/t/docker-and-disk-size/113453/1 "2017-12-28T14:04:46Z")
Hi, running ES 6.1.0 I have 10 nodes: 3 masters, 3 data, 3 coordinators, 1 ingest. The 10 nodes are running in docker on 3 hosts. The 3 hosts have 1.7TB of disk available. Kibana monitoring on the main cluster page claims that I have Disk Available: 17TB / 17TB (99.69%) Is that normal, does it affect the functionality in anyway? ---
**Author:** ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)\ **Post date:** [December 28, 2017, 6:37pm UTC](https://discuss.elastic.co/t/docker-and-disk-size/113453/2 "2017-12-28T18:37:52Z")
This looks wrong, how much disk are your elasticsearch nodes supposed to see in total? ---
**Author:** ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)\ **Post date:** [December 28, 2017, 6:38pm UTC](https://discuss.elastic.co/t/docker-and-disk-size/113453/3 "2017-12-28T18:38:46Z")
For the record, it should not be a problem until your nodes run out of disk space since Elasticsearch will not stop allocating new shards like it should do when a node runs out of disk space. ---
**Author:** ![javadevmtl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javadevmtl/32/45613_2.png) [@javadevmtl](https://discuss.elastic.co/u/javadevmtl)\ **Post date:** [December 28, 2017, 6:42pm UTC](https://discuss.elastic.co/t/docker-and-disk-size/113453/4 "2017-12-28T18:42:44Z")
Like I said, the hosts have 1.7 TB each, there is 3 hosts. There is 10 nodes running on the 3 hosts inside docker. Also only the master and data nodes have volumes mounted. ---
**Author:** ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)\ **Post date:** [December 28, 2017, 6:46pm UTC](https://discuss.elastic.co/t/docker-and-disk-size/113453/5 "2017-12-28T18:46:20Z")
OK, I thought 1.7TB was the free space. @dliappis I'm not familiar with Docker, does it ring a bell to you? ---
**Author:** ![javadevmtl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javadevmtl/32/45613_2.png) [@javadevmtl](https://discuss.elastic.co/u/javadevmtl)\ **Post date:** [January 2, 2018, 2:23pm UTC](https://discuss.elastic.co/t/docker-and-disk-size/113453/6 "2018-01-02T14:23:11Z")
@dliappis Hi, do you have any news on this? Thanks ---
**Author:** ![dliappis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dliappis/32/56174_2.png) [@dliappis](https://discuss.elastic.co/u/dliappis)\ **Post date:** [January 2, 2018, 4:36pm UTC](https://discuss.elastic.co/t/docker-and-disk-size/113453/7 "2018-01-02T16:36:26Z")
AFAIU there is no special Docker magic involved here. Basically you have 10 Elasticsearch processes running, spread across 3 hosts. Each host has 1.7TB of free disk space, so total disk space reported as available is 10 x 1.7 = 17TB. The % free will be always correct of course and this is what matters for the allocation algorithms and monitoring. Btw even if you run the Elasticsearch docker image without bind mounting any volume, the container will report available disk space for `/` based on the storage driver, e.g. in my case when using `overlay` the container reports the actual disk space free on my laptop: ```auto $ docker run --rm -ti docker.elastic.co/elasticsearch/elasticsearch-platinum:6.1.1 /bin/bash -c "df -h /" Filesystem Size Used Avail Use% Mounted on overlay 339G 213G 109G 67% / ``` ---
**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\ **Post date:** [January 3, 2018, 2:08am UTC](https://discuss.elastic.co/t/docker-and-disk-size/113453/8 "2018-01-03T02:08:23Z")
This is indeed not specific to Docker. The cluster stats that populate these metrics in Kibana are de-duplicated by publish address (which is not always effective if the nodes on the same host in fact have different publish addresses). See: [#24472](https://github.com/elastic/elasticsearch/issues/24472). ---
**Author:** ![javadevmtl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javadevmtl/32/45613_2.png) [@javadevmtl](https://discuss.elastic.co/u/javadevmtl)\ **Post date:** [January 3, 2018, 6:54am UTC](https://discuss.elastic.co/t/docker-and-disk-size/113453/9 "2018-01-03T06:54:32Z")
Ok, that's cool as long as allocation is not affected... ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 31, 2018, 7:08am UTC](https://discuss.elastic.co/t/docker-and-disk-size/113453/10 "2018-01-31T07:08:08Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.