# Disk space usage of /lib/docker is high

**URL:** https://meta.discourse.org/t/disk-space-usage-of-lib-docker-is-high/67375
**Category:** Self-hosting
**Tags:** server-resources
**Created:** [August 3, 2017, 12:12pm UTC](https://meta.discourse.org/t/disk-space-usage-of-lib-docker-is-high/67375 "2017-08-03T12:12:59Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [September 1, 2017, 11:32am UTC](https://meta.discourse.org/t/disk-space-usage-of-lib-docker-is-high/67375/9 "2017-09-01T11:32:02Z")

</div>

I encountered a similar issue; perhaps the same, it’s hard to tell. This is what fixed it (after a fashion) for me:

> [@Docker disk usage issue c. Sept 1 2017](https://meta.discourse.org/t/docker-disk-usage-issue-c-sept-1-2017/69194):
>
> If you do a fresh install, as I did recently for my [sandbox](https://discourse.angusmcleod.com.au/), you may, despite all the improvements in the cleanup scripts and docker itself, still encounter the dreaded disk usage creep issue; i.e. after rebuilding a number of times you see your disk usage go steadily upwards until the instance is no longer usable. This issue has had a number of iterations (hence ‘circa Sept 1 2017’). The current iteration seems to be un-removed aufs/diff files. Specifically, after a fresh Discourse install on…

---

_[View the full topic](https://meta.discourse.org/t/disk-space-usage-of-lib-docker-is-high/67375)._
