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

[画像] pfaffman: How much disk space do you have? $ df -h Filesystem Size Used Avail Use% Mounted on udev 476M 0 476M 0% /dev tmpfs 100M 8.9M 91M 9% /run /dev/mapper/vg-lv_root 19G 14G 4.1G 77% / tmpfs 497M …

My suggestion here then if you are ULTRA tight on space is just to go nuclear and and start from scratch. What is the output of docker ps, you basically need to kill your app container so you can free up the old base image.

$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 1fba0860cbc3 local_discourse/web_only "/sbin/boot" 5 months ago Up 29 minutes 0.0.0.0:80->80/…

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/mappp…

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

再構築時に空き容量の確保と埋め込みを繰り返すループに陥っている

サポートインストール

sam (Sam Saffron) 2018 年 8 月 31 日午前 1:00 16

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.

「いいね！」 3

トピック		返信	表示
Unable to rebuild discourse due to no space left on device Self-hosting	33	3232	2022 年 12 月 19 日
I got an error after updating my forked install Self-hosting unsupported-install	36	1910	2018 年 11 月 13 日
Upgrading when space seems low: stop app, then cleanup, then rebuild app? Self-hosting server-resources	6	445	2024 年 1 月 31 日
Discourse upgrade fails due to insufficient disk space on 25G droplet Self-hosting server-resources	39	1662	2022 年 3 月 30 日
My website is always down Self-hosting	46	1903	2022 年 4 月 22 日

再構築時に空き容量の確保と埋め込みを繰り返すループに陥っている

関連トピック