Add `soci index rm` command about soci-snapshotter HOT 5 CLOSED

Agree about rm --all. Users should probably have to work a little harder to shoot themselves in the foot. I would be in favor of adding a -q option to soci index list though (following the precedent set by nerdctl). Then users could say

soci index rm $(soci index list -q )

And soci index rm --ref <image-digest> would be nice.

from soci-snapshotter.

This was pointed at "3" after the following discussion:

This issue is just to delete the SOCI index manifest, but not delete the zTOCs. TBD whether zTOCs need to be cleaned up by hand (which would require a soci ztoc rm, as described above), or whether we would get all fancy and implement garbage collection of orphaned zTOCs.

A one-pager is probably needed to describe what we want the holistic artifact management experience to be, and then see what stories fall out of that.

But the immediate pain point is that if you create a second SOCI index for an image, but want soci push to upload the first one, you can't today.

from soci-snapshotter.

Request for clarification: Would this command also delete the zTOCs blobs contained in the index? What if the zTOCs are part of multiple SOCI indices (e.g., if it's from a base index layer used by multiple container images)? To do this right, we'd either have to sign up for reference counting, or periodic garbage collection sweeps.

Maybe that's the right thing to do. But maybe we should wait until we can use the containerd store to store the SOCI artifacts, rather than reinvent that wheel.

from soci-snapshotter.

My initial thought was that only index blobs would be deleted + entry deleted from the db. Ztoc deletion should be part of soci ztoc rm command. That does raise the question of what happens to indexes if ztocs are deleted. I don't have the answer to that.

from soci-snapshotter.

3

from soci-snapshotter.