# Upgrade failed: low disk space -- excess overlay files?

**URL:** <https://meta.discourse.org/t/upgrade-failed-low-disk-space-excess-overlay-files/287048>\
**Category:** Self-hosting\
**Tags:** server-resources\
**Created:** [November 30, 2023, 8:31am UTC](https://meta.discourse.org/t/upgrade-failed-low-disk-space-excess-overlay-files/287048 "2023-11-30T08:31:57Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [November 30, 2023, 10:09am UTC](https://meta.discourse.org/t/upgrade-failed-low-disk-space-excess-overlay-files/287048/4 "2023-11-30T10:09:34Z")

</div>

> [@ToddZ](#):
>
> Apparently because of two 18G “overlay” files:

You don’t have two 18GB overlay files, that’s a red herring. Docker uses overlayfs and those are just how your existing disk is presented to the container. `/dev/vda2` is your disk and is mounted at `/` - that’s where you should be directing your efforts.

If `./launcher cleanup` did nothing then I’m assuming `docker image prune` (removes dangling images) won’t either. If you’re only using this server for discourse you may need to just check around to make sure there are no large files/folders in your home directory.

---

_[View the full topic](https://meta.discourse.org/t/upgrade-failed-low-disk-space-excess-overlay-files/287048)._