[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.

[image] tobiaseigen: ./docker rebuild app [image] No I haven’t edited it recently. The website crashed yesterday and I ran the cleanup and then ran rm /var/discourse/shared/standalone/backups/default/* Then I rebuilt using ./launcher rebuild app The website started working again after that and now it’s back to being dead.

Sorry I meant ./launcher rebuild app So you are doing the the right things.

Have you had a look at Discourse Doctor?

[image] Okay, so it is a storage issue. How do I make space now? I’m sorry but I’m a beginner. I just ran discourse-doctor and I was left with multiple lines stating that my storage was full. [image]

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 ```

Unable to rebuild discourse due to no space left on device

Product Support Self-hosting

tobiaseigen (Tobias Eigen) January 2, 2021, 5:31am 2

Did you try just doing a

./docker rebuild app

and seeing what happens? I think git pull is no longer required first.

Otherwise it looks like you may need to review your app.conf file. Have you edited it recently?

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