[image] I get the aforementioned error while attempting to do an operation. I have no idea as to why this is happening.

[image] littleviolette: I have backups set up on DO Spaces Either you don’t have backups on spaces or you didn’t delete the local backups when you switched to it. You can delete those backups and be in good shape.

Do you have anything else on the server? If not, it’s probably discourse backups that you can delete.

Can you go over the process of deleting backups coz I’ve never really understood the process. I wanna be sure once and for all because I’ve been having storage issues for a really long time. No, I don’t have anything else on the server.

A good first step is to run ./launcher cleanup If that doesn’t work, try ./discourse-doctor If you still have difficulties, you can look at deleting old backups from /var/discourse/shared/standalone/backups/default Let us know how these work out for you!

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: 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): 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

[image] neounix: Kindly post the output as text (copy-and-paste) using fenced markdown. Terminal screenshot images are hard to read on mobile. @neounix local_discourse/app latest 674fd54f165f 4 minutes ago 2.5GB f3a4104c3f75 22 hours ago 2.5GB discourse/base 2.0.20201221-2020 c0704d4ce2b4 11 days ago 2.11GB ```

Hey @seshu_ram FYI and FWIW: You can remove this orphan image and reclaim a bit more disk space: f3a4104c3f75 docker image rm f3a4104c3f75 The launcher cleanup process does not (as I recall) remove images less than 24 hours old. Or, you can run cleanup again in a few hours, as you please.

One thing I’ve noticed is that recent command line updates of Discourse are eating quite a bit of disk space.. 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 :wink: 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? :thinking:

Kind of unavoidable I think we bumped base image 2 times in the last few months. Not much we can do. Looks like the cleanup on your server shaved off 2 base images.

anon43908006: Whats the easy way to rebuild a discourse server and reinstall letsencrypt please? @anon43908006, there is a guide at: [image] Change the domain name or rename your Discourse Self-Hosting bookmark This guide explains how-to change the domain name of your Discourse site, and includes information about setting up DNS changes, editing configuration files, updating site settings, and correcting social logins and post content to reflect your new domain name. warning This guide is for self-hosted Discourse instances that were installed using our installation guide on GitHub. If you are hosted by Discourse, please see Configure your domain name for hosted Discourse for specific … It goes over many considerations for changing your domain, check it out. :slight_smile:

Unable to rebuild discourse due to no space left on device

Product Support Self-hosting

seshu_ram (Seshank K) January 2, 2021, 6:20am 12

This worked. My website is live now. Thank you so much. Thanks a lot for your time! That helped a lot.

@tobiaseigen

Topic		Replies	Views
My website is always down Self-hosting	46	2909	April 22, 2022
I got an error after updating my forked install Self-hosting unsupported-install	35	2344	November 13, 2018
Stuck in a loop of freeing up space and filling it up again when rebuilding Self-hosting server-resources	30	4344	March 20, 2019
Errno::ENOSPC: No space left on device Product Support docker	16	14261	June 1, 2017
Discourse upgrade fails due to insufficient disk space on 25G droplet Self-hosting server-resources	38	2349	March 30, 2022

Unable to rebuild discourse due to no space left on device

Related topics