Replies: 2 comments 3 replies
-
You might try allowing the image store to discard the unpacked layers? You'll need to provide your own containerd.tomp.tmpl, as described in the docs:
Add a line in the |
Beta Was this translation helpful? Give feedback.
-
Thanks for the idea. Finally got round to it today while trying other idea before this. Unfortunately it makes no difference at all. Example numbers - size of /var/lib/rancher/: Using docker with Docker image format files: 9 GB Any other ideas to get the disk space down to the same level as docker please? |
Beta Was this translation helpful? Give feedback.
-
k3s 1.29.3.
All comparisons are on two freshly installed identical CentOS VMs. The only difference is the docker/containerd setting.
I was using
--docker
when starting k3s, coupled withdocker load
. Testing performance I found that not using--docker
(and thus containerd) with/usr/local/bin/k3s ctr images import
gave me a needed small performance increase. Also containerd seems to be the standard nowadays.What I've found is that
/var/lib/rancher/k3s/agent/containerd
is taking twice the space that/var/lib//var/lib/docker/overlay2
used to take.Using docker:
Using containerd:
Using
du
on /var/lib/ is about 17G on either. But I think du is counting things twice. Usingdu -x
shows docker at 8G and containerd at 14G.This doubling of space is a problem where I am using k3s where I can't increase the disk space.
Any ideas please?
Beta Was this translation helpful? Give feedback.
All reactions