https://blue-build.org/ logo
Excessive storage usage in /var/lib/containers/sto...
# questions
a
message has been deleted
k
Hi there, something seems to be wrong with my installation, but I am not sure where to go from here on finding out how to fix it. I have my installation on an SSD showing 812GB on this partition (in gparted). I have a couple games installed. Some flatpaks. The storage on all these looks normal. Overall, my home folder shows as 230-250 GB (230 by
du
, 245 in FileLight). The rest of my system usage is weird.
Copy code
`bash
sudo df -h /var
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda4       813G  681G  128G  85% /var
681G-245G is 436, so the rest of my system is taking... 400G+ of space? I found the tool [btdu](https://github.com/CyberShadow/btdu) to help scan what's taking space. So far it has scanned that
/var00/lib/containers/storage/overlay
is 366GB. It looks like maybe there is some duplication/remnants sticking around in here. There are 11 sub-folders in here that are around 9GB in size, and all contain installations for the same applications. I do my builds with
bluebuild build
locally and push the images to ghcr.
Copy code
bash
rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: last run 53min ago
Deployments:
ā— ostree-unverified-registry:ghcr.io/xxx/uxxx:latest
                   Digest: 
                  Version: 42.251228 (2025-12-28T22:11:13Z)

  ostree-unverified-registry:ghcr.io/xxx/uxxx:latest
                   Digest: 
                  Version: 42.251207 (2025-12-07T00:56:36Z)
No pinned images sticking around. I've also tried all the subcommands/options of
rpm-ostree cleanup
and
bluebuild prune
. Is there something obviously wrong in all of this? Hoping to understand what on earth is going on here. Thanks. https://cdn.discordapp.com/attachments/1462225209565122600/1462225209930023137/image.png?ex=696d6ad8&is=696c1958&hm=ef5bbc6b189c10c34bf2013783881de19285c93d34d5294dea16c130487f90db&
g
You can make use of
bluebuild prune
along with
-B
for any driver you use like
podman
in your instance
Oh you said you did that
That might be the root container storage so I would suggest running
sudo podman system prune
to clean that up
k
I did try that at one point in the past, but I'll try it again and report back
Okay I guess I didn't try that one before! It looks like that did cut down about 100 or so GB. There's still some duplicate-looking folders in /overlay (the 9gb for instance I can now see 3 of, all with the same/similar contents, instead of 11) and it's about 275GB now. I'm trying that with a few of the options again and will see.
a
message has been deleted
2 Views