My rebuild failed due to lack of disk space so I need to free up some space. But I’m stuck in a loop: ./launcher cleanup frees up sufficient space to be above 5 GB. So I start a rebuild but that then fills up the recovered space again so that it fails to complete. See below. How do I get things run…

docker rm -f aa6b422d88ca docker rm -f 1fba0860cbc3 ./launcher cleanup ./launcher rebuild data ./launcher rebuild web_only But really the root cause here is that you are just way too tight on disk space. I would recommend doubling the size /dev/mappper/vg-lv_root

The last step (rebuild web_only) fails: Bundle complete! 110 Gemfile dependencies, 201 gems now installed. Gems in the group development were not installed. Bundled gems are installed into `./vendor/bundle` I, [2018-08-31T00:50:57.518677 #13] INFO -- : > cd /var/www/discourse && su discourse -c '…

[이미지] tophee: Gem::LoadError: can’t activate public_suffix-2.0.5, already activated public_suffix-3.0.2 /var/www/discourse/lib/plugin_gem.rb:18:in `load Hmmmm … are you on tests passed… stable or beta? Also, remove discourse-sync-to-dropbox asap. It looks like it is not working at the moment…

Phew! After removing the dropbox plugin my site is finally back up and running. Thanks a lot to everyone for your support! [이미지] sam: are you on tests passed… stable or beta? Since I never changed that, I guess I’m on tests-passed. [이미지] sam: I would recommend doubling the size /dev/map…

10GB is ambitious and absolutely not the case if you are running seperate data and web containers.

[이미지] sam: absolutely not the case if you are running seperate data and web containers Ah, I see. I don’t think that was mentioned anywhere. I’ll check tomorrow where that information might be usefully added. However, the situation seems to look much brighter now: $ df -h Filesystem …

The data container was using the old image, so you had a situation where: “data container” was saying HEY I need the old Discourse base image “web container” was saying I need the new image Not sure where all the space came from but this is a chunk of it.

[이미지] sam: “data container” was saying HEY I need the old Discourse base image “web container” was saying I need the new image How did that happen? From my side, I can say that I started an update via /admin/upgrade which failed, presumably due to a lack of space. Since the website was down…

[이미지] tophee: How did that happen? Because you hadn’t upgraded the data container. [이미지] tophee: I wonder if the web-updater could not handle lack of disk space better. It could probably do a disk space check before it started, and refuse to proceed if there wasn’t enough space.

Another question: Where did you get these IDs from: [이미지] sam: aa6b422d88ca […] 1fba0860cbc3

Those are the container IDs (first column in the docker ps output).

Stuck in a loop of freeing up space and filling it up again when rebuilding

지원 자체 호스팅

tophee (Christoph) 8월 31, 2018, 1:27오전 23

Another question:

Where did you get these IDs from:

글		댓글	조회수
Unable to rebuild discourse due to no space left on device Self-hosting	32	3562	11월 19, 2022
I got an error after updating my forked install Self-hosting unsupported-install	35	2132	11월 13, 2018
Running out of space - Docker image is large? Support	9	383	6월 1, 2026
Upgrading when space seems low: stop app, then cleanup, then rebuild app? Self-hosting server-resources	5	564	1월 31, 2024
Discourse upgrade fails due to insufficient disk space on 25G droplet Self-hosting server-resources	38	2071	3월 30, 2022

Stuck in a loop of freeing up space and filling it up again when rebuilding

Related topics