# 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:** 10

<div class="post-metadata">

**Author:** ![neounix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/neounix/32/215617_2.png) [@neounix](https://meta.discourse.org/u/neounix)\
**Post date:** [January 2, 2021, 5:51am UTC](https://meta.discourse.org/t/unable-to-rebuild-discourse-due-to-no-space-left-on-device/174774/10 "2021-01-02T05:51:03Z")

</div>

Hi @seshu_ram

Often, when containers are rebuilt, the process leaves orphan images. If you have rebuilt your container often, these images can take up a lot of space.

In fact, these orphan images recently took up nearly 100 GB + on our server until I deleted them. You can easily check.

Please post the output of:

```plaintext
docker images

```

Kindly post the output as text (copy-and-paste) using fenced markdown. Terminal screenshot images are hard to read on mobile.

Thanks.

Note:

Please note that `launcher cleanup` also prunes these orphans (based on 24 hours in the past, I think):

```bash
if tty >/dev/null; then
      read -p "Would you like to attempt to recover space by cleaning docker images and containers in the system? (y/N)" -n 1 -r
      echo
      if [[$REPLY =~ ^[Yy]$ ]]
      then
        $docker_path container prune --force --filter until=1h >/dev/null
        $docker_path image prune --all --force --filter until=1h >/dev/null
        echo "If the cleanup was successful, you may try again now"
      fi
    fi

```

---

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