The Dependency Proxy to associate blobs with their respective manifests

Release notes

You've been using the Dependency Proxy and you have noticed that several key features are missing. For example, you may want to:

• Display how much space an individual image takes up.
• Delete a single image from the cache.
• Run garbage collection

Well, one key feature that is required to unblock all of the above functionality is the ability to understand which blobs are related to which manifests. What does that mean? A container image consists of layers (blobs) and a manifest, which you can think of as a recipe for the image. The proxy didn't have a way of associating those two pieces. So presenting how much space is being used by an image is difficult.

Moving forward, we've added some backend functionality that associates the image's manifest with it's layers or blobs. This means that we can tackle some of the aforementioned features in upcoming milestones.

Problem to solve

The Dependency Proxy currently has no way of associating an image's manifest with it's respective layers. This prevents us from implementing any feature that relies on this data being connected.

Proposal

Implement a way for an image's manifest to be associated with it's layers, so that we can build features like garbage collection and displaying more granular storage usage of the proxy.