stargz-snapshotter mounts a special image format stargz (which compatible with original OCI image, but with additional index info for fuse mounting), and convert read()/write() call to HTTP range requests to registry. So I wonder will HTTP range requests lead to many small files on disk?
I am trying to integrate stargz-snapshotter with dragonfly. It works.
stargz-snapshotter mounts a special image format stargz (which compatible with original OCI image, but with additional index info for fuse mounting), and convert read()/write() call to HTTP range requests to registry. So I wonder will HTTP range requests lead to many small files on disk?
Related: https://github.com/containerd/stargz-snapshotter/issues/92