# Update failed. Low disk space and database version discrepancy

**URL:** <https://meta.discourse.org/t/update-failed-low-disk-space-and-database-version-discrepancy/351076>\
**Category:** Product Support\
**Created:** [February 7, 2025, 2:23pm UTC](https://meta.discourse.org/t/update-failed-low-disk-space-and-database-version-discrepancy/351076 "2025-02-07T14:23:55Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [February 7, 2025, 5:51pm UTC](https://meta.discourse.org/t/update-failed-low-disk-space-and-database-version-discrepancy/351076/2 "2025-02-07T17:51:31Z")

</div>

Did you answer yes to letting it get rid of the unused containers? There’s a reasonable chance that’ll restore a bunch of space.

You can do a `./launcher cleanup`. You should first do a `./launcher start app` and make a backup. That way, if things go south you can just spin up a new server and restore the backup. If your server has been around, it might be time for a new OS anyway.

---

_[View the full topic](https://meta.discourse.org/t/update-failed-low-disk-space-and-database-version-discrepancy/351076)._