K3s eating too much disc space #11802
Replies: 2 comments
-
When something similar happened to me, it was because k3s wasn't triggering image garbage collection soon enough (that is, deleting old container images that are not used anymore). If I remember correctly, by default, it triggers only when 80% of the storage space is used. To fix this, I added these lines to my config (
That way it, it doesn't trigger below 20% of storage used, and always triggers when more than 50% is used. |
Beta Was this translation helpful? Give feedback.
-
@MrTrustor is correct. You're not using enough space to trigger cleanup. Default thresholds are 85% high, 80% low. This is covered in the upstream Kubelet image GC threshold documentation. |
Beta Was this translation helpful? Give feedback.
-
**Hello Guys , i have been running k3s for a while now with about 100 workloads and it seems like k3s has been eating much of my disc space for some reason.
i am running k3s version v1.31.4+k3s1 (a562d09)
go version go1.22.9.
I would appreiate it if someone could tell me how to fix this without losing data **
Beta Was this translation helpful? Give feedback.
All reactions