Why does k3s mount very old (and useless) snapshots in the overlayfs

I’m running Debian Bullseye app on Scale.

Check out the root overlayfs reference to dozens of obsolete and useless upper directories (which it mounts as a long list of lower directories):

# mount
overlay on / type overlay (rw,relatime,lowerdir=/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5810/fs:/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5809/fs:/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5808/fs:/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5807/fs:/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5806/fs:/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5805/fs:/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5804/fs:/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5803/fs:/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5802/fs:/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5801/fs:/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5800/fs:/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5799/fs:/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5798/fs:/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5797/fs:/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5796/fs:/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5795/fs:/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5794/fs:/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5793/fs:/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/5788/fs,upperdir=/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/6051/fs,workdir=/mnt/main/ix-applications/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/6051/work,uuid=on)

This is ridiculous. I recently deleted and then reinstalled the app and it is referencing snapshots from days ago in the mount. I realize this isn’t harmful, but that’s ridiculous.

Is there some way to gracefully clean up all these overlay filesystem files that are generated each time you start a new instance? They are completely useless, but if you try to manually delete the files, k3s is very unhappy and won’t start your app.

I know this is supposed to be automatically garbage collected when you hit 80% of your space allocation, but that’s ridiculous.