I’ll be interested to know what’s the meaning of the <none>
docker image. (Edit: it seems, if a <none>
image shows up in docker images -a
that’s not too important, but if it shows up in docker images
then it is a waste of space. I would hope launcher cleanup would help, but it hasn’t helped you…)
Note that the overlay filesystem usage as seen by df matches the usage of the root filesystem: there’s a lot of data doing double duty and you need to take care not to double-count. In your case the available space is 3.2G and that’s the figure to worry about. There might well be some tidying up to do.
I’ll show my similar stats below. I have two forums, each on a different host. One host has 20G and the other has 25G of space. I think 15G might prove to be very tight, especially when the update process demands 5G free space before starting.
# df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 25G 19G 5.1G 79% /
# docker images -a
REPOSITORY TAG IMAGE ID CREATED SIZE
local_discourse/app latest 8da0107aba03 2 months ago 2.7GB
discourse/base 2.0.20210415-1332 30e4746e631e 3 months ago 2.23GB
<none> <none> 1e6bf44c2762 5 months ago 2.46GB
discourse/base 2.0.20201221-2020 c0704d4ce2b4 7 months ago 2.11GB
# du -shc /var/lib/docker/overlay2/*/diff
2.2G /var/lib/docker/overlay2/05fa0e4df2...
76M /var/lib/docker/overlay2/58b000b1f5c...
20K /var/lib/docker/overlay2/6271023fc7a...
1.1G /var/lib/docker/overlay2/6271023fc7...
2.3G /var/lib/docker/overlay2/91d6adf7ad...
481M /var/lib/docker/overlay2/b6b06a7cee...
592M /var/lib/docker/overlay2/d81e44d563...
76M /var/lib/docker/overlay2/fb98649680b...
6.8G total
# du -shc /var/lib/docker/overlay2/*
2.2G /var/lib/docker/overlay2/05fa0e4df2...
76M /var/lib/docker/overlay2/58b000b1f5c...
4.7G /var/lib/docker/overlay2/6271023fc7...
40K /var/lib/docker/overlay2/6271023fc7a...
2.3G /var/lib/docker/overlay2/91d6adf7ad...
481M /var/lib/docker/overlay2/b6b06a7cee...
592M /var/lib/docker/overlay2/d81e44d563...
76M /var/lib/docker/overlay2/fb98649680b...
36K /var/lib/docker/overlay2/l
11G total
# docker system df
TYPE TOTAL ACTIVE SIZE RECLAIMABLE
Images 4 1 5.155GB 4.689GB (90%)
Containers 1 1 1.059GB 0B (0%)
Local Volumes 0 0 0B 0B
Build Cache 0 0 0B 0B
See perhaps also Fixing discourse after disk full :