Replies: 2 comments
-
The snapshot key used by the unpacker is determined by the hash of the tar stream(s) being unpacked into the snapshotter. A key collision occurs when the layer content is exactly the same with the same hash. First can you use |
Beta Was this translation helpful? Give feedback.
-
containers' rootfs writable layer also count as an Active layer and resides in /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots...If you have lots of containers running maybe you can try draining all containers on the node and see if the problem still exists |
Beta Was this translation helpful? Give feedback.
-
Hi,
we run a Kubernetes cluster and saw root volumes filling up in the following folder on our nodes:
/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots
The container images are very similar, they all share the same layers.
One of the layers, which is used most often, has a size of 332.6 MiB (tar.gz).
When we take a look at the
snapshots
folder, we see the identical layer unpacked multiple times (436.1 MiB):Here are the layer blobs on the same node:
We would have expected the default snapshotter overlayfs to unpack the layer only once, but well, it keeps unpacking, the more containers are added to the node.
redirect_dir
flag?Thank you so much for your help!
Configuration:
Beta Was this translation helpful? Give feedback.
All reactions