Hi there, I’m trying to rebuild Discourse but I’m running into this error: FAILED -------------------- RuntimeError: cd /var/www/discourse && su discourse -c 'bundle exec rake assets:precompile' failed with return #<Process::Status: pid 4266 exit 1> Location of failure: /pups/lib/pups/exec_command…

I need to start running cleanup from a lightweight image … what does docker images return … do a docker rmi on the old discourse image … also 7 gigs is really tight considering our images are 1.5gigs (once you factor in bootstrapping and so on)

Weirdly, I seem to be out of disk space indeed: ubuntu@discourse:/var/discourse$ df -h Filesystem Size Used Avail Use% Mounted on /dev/xvda1 7.8G 6.7G 700M 91% / none 4.0K 0 4.0K 0% /sys/fs/cgroup udev 996M 12K 996M 1% /dev tmpfs 201M 356K …

can you start with a ./launcher cleanup I bet you have 2 docker images going

Thanks, @sam , but that unfortunately didn’t solve the problem: ubuntu@discourse:/var$ cd /var/discourse/ ubuntu@discourse:/var/discourse$ sudo ./launcher cleanup The following command will - Delete all docker images for old containers - Delete all stopped and orphan containers Are you sure (Y/n):…

ubuntu@discourse:/var/discourse$ sudo docker images REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE local_discourse/app latest 9698d6e190bb 49 minutes ago 1.929 GB <none> <none> 48086d6c592e …

[изображение] avorio: 48086d6c592e 537dec28027b aa2b4af001ab do a docker rmi on those images.

Done. All deleted. Here’s the disk space situation: ubuntu@discourse:/var/discourse$ df -h Filesystem Size Used Avail Use% Mounted on /dev/xvda1 7.8G 4.5G 2.9G 61% / none 4.0K 0 4.0K 0% /sys/fs/cgroup udev 996M 12K 996M 1% /dev tmpfs 201M 3…

My guess… somehow these failed builds are leaving behind an image, we should investigate that @mpalmer at some point. Also another possibility is that you are running an old version of bash and launcher is relying on features you do not have.

[изображение] sam: My guess… somehow these failed builds are leaving behind an image, we should investigate that @mpalmer at some point. But the first failure was caused by lack of disk space. There was no other cause for failure, which suggests to me that your assumption is not correct. Are …

This is still a problem. Today I have same Errno::ENOSPC: No space left on device I was rebuilding app a few times before this error occur. ./launcher cleanup helped

@sam I’m trying to remove an existing image but I can’t seem to remove it root@ip-172-31-27-60:/var/discourse# docker images REPOSITORY TAG IMAGE ID CREATED SIZE local_discourse/app latest 2bc4af777b30 12 days ago 2.284…

Errno::ENOSPC: No space left on device

Поддержка

Falco (Falco) 21.Декабрь.2016 13:05:24 13

Do a backup and then:

Тема		Ответов	Просм.
Unable to rebuild discourse due to no space left on device Self-hosting	33	3315	19.12.2022
Docker installation not working Self-hosting	17	5306	05.11.2016
My website is always down Self-hosting	46	2104	22.04.2022
I got an error after updating my forked install Self-hosting unsupported-install	36	2000	13.11.2018
My forum stop working... could not do Rebuild App Self-hosting	5	1250	01.03.2022

Errno::ENOSPC: No space left on device

Связанные темы