# Unable to rebuild discourse due to no space left on device

**URL:** <https://meta.discourse.org/t/unable-to-rebuild-discourse-due-to-no-space-left-on-device/174774>\
**Category:** Self-hosting\
**Created:** [January 2, 2021, 4:59am UTC](https://meta.discourse.org/t/unable-to-rebuild-discourse-due-to-no-space-left-on-device/174774 "2021-01-02T04:59:55Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [February 10, 2022, 9:06pm UTC](https://meta.discourse.org/t/unable-to-rebuild-discourse-due-to-no-space-left-on-device/174774/14 "2022-02-10T21:06:56Z")

</div>

One thing I’ve noticed is that recent command line updates of Discourse are eating quite a bit of disk space..

```plaintext
root@endoffice-b:/var/discourse# ./launcher cleanup
WARNING! This will remove all stopped containers.
Are you sure you want to continue? [y/N] Y
Total reclaimed space: 0B
WARNING! This will remove all images without at least one container associated to them.
Are you sure you want to continue? [y/N] Y
Deleted Images:
deleted: sha256:284403a252ba061b3ab97f4bfe293ac5e8f05f39ada429d718f58e56191251c2
deleted: sha256:6b6899d54d4dd1f21568956b652975f7c0b9e439978b8cc53036efc46baaf971
untagged: discourse/base:2.0.20211118-0105
untagged: discourse/base@sha256:74b41fffd4f05433eb7c9b72954b1f5f8b15cd0e802bb724c96b7d699c3f6fa1
deleted: sha256:b6cc7cf8974a6ef7bb64c36f4592af261cda0d5565bd91da603568ce26968048
deleted: sha256:c1455b2fdbca024c36c4e75746051b77c3637020cfa1e36a41440292a8c39424
deleted: sha256:77b323d4ec74aad770337f99a60e862a64ccc53f4775b5f4945df0e606f78b90
untagged: discourse/base:2.0.20220128-1817
untagged: discourse/base@sha256:dcb4eb8e41a2e84f776f80587f308d167a54ad7ff4ba616199891828bbd4ddae

Total reclaimed space: 3.54GB

```

This happened on both instances, the other was 3.538GB 😉

I’m usually pretty religious about running `./launcher cleanup` after each Discourse update, and I update about once a month, so that says to me the last update _by itself_ ate nearly 4GB of disk.. cc @falco @sam is this something we should be concerned about? 🤔

---

_[View the full topic](https://meta.discourse.org/t/unable-to-rebuild-discourse-due-to-no-space-left-on-device/174774)._
