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

[이미지] 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.

[이미지] 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 <none> <none> f3a4104c3f75…

[이미지] tobiaseigen: Let us know how these work out for you! This worked. My website is live now. Thank you so much. Thanks a lot for your time! That helped a lot. @tobiaseigen

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 wil…

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: [이미지] Change the domain name or rename your Discourse Self-Hosting bookmark This guide explains how-to change the domai…

[이미지] codinghorror: is this something we should be concerned about? :thinking: [이미지] sam: Not much we can do. To clarify, is there not much to do about the overall size of the upgrades increasing, or not much to do about the recent spike in bumping base image activity (which will not a…

I asked @falco about this in chat and he said lately we’ve had a lot of base image changes due to dependencies being updated, so there’s been a higher than usual amount of disk space in upgrades in the last ~6 months.

Sorry to hear you’ve run into trouble changing your domain name, @anon43908006. Because this is Support , I encourage you to create a new topic that explains your exact case: it may be that your situation requires more discussion than what’s happening in this topic, which is more of a general patter…

I get the same No space left on device error when I try to backup my Discourse: [2022-11-15 08:23:38] EXCEPTION: /var/www/discourse/lib/discourse.rb:131:in `exec': Failed to gzip archive. gzip: /var/www/discourse/public/backups/default/forum-leasehackr-2022-11-15-080439-v20221110175456.tar.gz: No …

디스크 공간 부족으로 Discourse 재빌드 실패

제품 지원 자체 호스팅

maiki (maiki) 4월 4, 2022, 7:56오후 17

@anon43908006, 가이드가 여기에 있습니다:

도메인 변경 시 고려해야 할 많은 사항들을 다루고 있으니 확인해 보세요.

글		댓글	조회수
My website is always down Self-hosting	46	2828	4월 22, 2022
I got an error after updating my forked install Self-hosting unsupported-install	35	2281	11월 13, 2018
Stuck in a loop of freeing up space and filling it up again when rebuilding Self-hosting server-resources	30	4269	3월 20, 2019
Errno::ENOSPC: No space left on device Product Support docker	16	14244	6월 1, 2017
Discourse upgrade fails due to insufficient disk space on 25G droplet Self-hosting server-resources	38	2295	3월 30, 2022

디스크 공간 부족으로 Discourse 재빌드 실패

Related topics