Well, sigh – I’m stuck on a failed upgrade.
I’m on a 25G VPS, using the supported Docker installation.
Upgrading docker_manager via the admin panel went fine.
Upgrading Discourse from v3.2.0.beta1 +125 to v3.2.0.beta3 +325 via the admin panel failed, so I tried a command line install:
cd /var/discourse
git pull
./launcher rebuild app
…which also failed:
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/vda2 23G 22G 640M 98% /
Apparently because of two 18G “overlay” files:
root@forum:/var/discourse# df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 95M 1.4M 94M 2% /run
/dev/vda2 23G 18G 4.1G 82% /
tmpfs 474M 0 474M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/vda1 511M 6.1M 505M 2% /boot/efi
tmpfs 95M 4.0K 95M 1% /run/user/0
overlay 23G 18G 4.1G 82% /var/lib/docker/overlay2/8a331589d7fa9046a6ef73489cc830c2583cb76c9174125c8bfe1064d58cd503/merged
overlay 23G 18G 4.1G 82% /var/lib/docker/overlay2/d56574358c8edbc9bc1fb50022585b854462a8ce56daa636b07f3a3771949251/merged
(Three 18G files on a 25G server? That’s 54G…)
It seems something is reclaimable:
root@forum:/var/discourse# docker system df
TYPE TOTAL ACTIVE SIZE RECLAIMABLE
Images 2 2 4.3GB 3.334GB (77%)
Containers 2 2 1.849GB 0B (0%)
Local Volumes 0 0 0B 0B
Build Cache 0 0 0B 0B
…but I’m not sure what or how.
Contents of /var/discourse/shared/standalone/backups/default
only amount to 67Mb.
I stopped docker with systemctl stop docker
and tried these to no effect:
docker system prune -a
docker buildx prune --all
docker builder prune --all
…all reported 0B freed.
I have two Docker images, one for Discourse and one for… “none?”
root@forum:/var/discourse/image# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
local_discourse/app latest 5ff1dcfe050c 2 months ago 4.09GB
<none> <none> bbaceb5f4a80 2 months ago 214MB
Apparently “none” indicates a dangling or intermediate image: Why the “none” image appears in Docker and how can we avoid it - Stack Overflow – but it’s so small I don’t think it’s my first priority.
When advice at Is it safe to clean docker/overlay2/ - Stack Overflow gets into grepping overlays against images, I lose steam. There are 60 hashed folders in my docker/overlay2… please don’t make me grep 120 times…
I imagine my options at this point are:
A. Get some help figuring out if either of these overlays can be deleted.
B. Restore from a snapshot, upgrade for more disk space and try again. Will I always have these huge overlays?
(And how do I even have 3 x 18G files on a 25G instance…?)
If anyone’s up at this hour and has any input, I’d appreciate it.