Hey folks, I am running the official docker setup. So far so gut. I was always able to update everything from the web interface. I am on 2.9.0.beta1 and 2.9.0.beta2 is available. Suddenly I see this: You are running an old version of the Discourse image. Upgrades via the web UI are disabled until you run the latest image. To do so log in to your server using SSH and run: cd /var/discourse git pull ./launcher rebuild app More info on our support site No problem I think, but when execute the ./launcher rebound app command but nothing happens afterwards: root@test:~# cd /var/discourse/ root@test:/var/discourse# git pull remote: Enumerating objects: 7, done. remote: Counting objects: 100% (7/7), done. remote: Compressing objects: 100% (1/1), done. remote: Total 4 (delta 3), reused 3 (delta 3), pack-reused 0 Unpacking objects: 100% (4/4), 560 bytes | 140.00 KiB/s, done. From https://github.com/discourse/discourse_docker dc5b37c..65fa205 main -> origin/main Updating dc5b37c..65fa205 Fast-forward templates/web.template.yml | 6 ++++++ 1 file changed, 6 insertions(+) root@test:/var/discourse# ./launcher rebuild app x86_64 arch detected. You have less than 5GB of free space on the disk where /var/lib/docker is located. You will need more space to continue Filesystem Size Used Avail Use% Mounted on /dev/sda1 19G 14G 4.7G 74% / Would you like to attempt to recover space by cleaning docker images and containers in the system? (y/N)y If the cleanup was successful, you may try again now root@test:/var/discourse# root@test:/var/discourse# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES c4830c85abab local_discourse/app "/sbin/boot" 2 months ago Up 31 hours 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp app How much space do I need in order to update? root@test:/var/discourse# df -h Filesystem Size Used Avail Use% Mounted on udev 949M 0 949M 0% /dev tmpfs 194M 796K 193M 1% /run /dev/sda1 19G 11G 7.6G 58% / tmpfs 968M 0 968M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 968M 0 968M 0% /sys/fs/cgroup /dev/sda15 253M 1.1M 252M 1% /boot/efi overlay 19G 11G 7.6G 58% /var/lib/docker/overlay2/1ab2396bdd0b9c2fbc6110cdcc792dba2c2bc8a52650935ff7af0084bda62f07/merged tmpfs 194M 0 194M 0% /run/user/0 I have more than 5GB available but it does not work.

Those backups are just ~ 10 MB. But I could clean up some more logs in journal. Got it working. The 5GB space requirement is AFTER pulling and extracting the images. I guess I need to add more storage to that server.

Run ./launcher cleanup and then try again

I did that already. Nothing to clean up left. Also cleaned up journal logs which were 1-2 GB.

Docker update not working due to space requirements?

Product Support Self-hosting

pfaffman (Jay Pfaffman) February 18, 2022, 11:54pm 4

Did you rebuild after it did the cleanup?

You might try deleting a backup or two.

Topic		Replies	Views
Cannot upgrade to latest version, disk full Self-hosting server-resources	10	884	February 3, 2023
Can't rebuilt app, says you have less than 5GB space on the disk Self-hosting server-resources	2	1695	January 17, 2019
Website showing 504 error after trying to update to 2.6.0 beta2 Self-hosting	1	641	August 23, 2020
Site Not Functioning After Attempted Upgrade Self-hosting	5	1247	December 9, 2019
I got an error after updating my forked install Self-hosting unsupported-install	35	2343	November 13, 2018

Docker update not working due to space requirements?

Related topics