The OCI spec defines an Image Index concept to handle multiple manifests in an OCI image. Currently, we expose an Image interface that is consumed no matter the implementation (daemon, registry or layout), this is very convenient to decouple the implementation.
Requeriment
This issue suggests the definition and implementation of a new interface to expose the operations to deal with an Image Index .
Proposal
Note: I am using underscore to refer to a package, for example, foo_Bar referes to a Bar class in the foo package
Context
The OCI spec defines an Image Index concept to handle multiple manifests in an OCI image. Currently, we expose an Image interface that is consumed no matter the implementation (daemon, registry or layout), this is very convenient to decouple the implementation.
Requeriment
This issue suggests the definition and implementation of a new interface to expose the operations to deal with an Image Index .
Proposal
Note: I am using underscore to refer to a package, for example, foo_Bar referes to a Bar class in the foo package
Notes
imgutil.remote
package in amanifest_list.go
file