A collection of definitions and terms used within this repository.
The owner of an artifact format. The OCI Image Spec is owned by the OCI working group.
An artifact is defined to be unique by its config.mediaType.
See Registry
Vendors that implement and/or run the OCI Distribution Spec.
The uniqueness of an artifact is defined by its type. An artifact has a type, which has a collection of layers.
The Artifact is defined as unique by its manifest.config.mediaType. Layers are defined by their layer.config.mediaType.
OCI Image is a specific type of artifact. However, an OCI image is not meant to define all artifacts. Tooling, such as docker, containerD and vulnerability scanners that perform security checks upon container images, use the config.mediaType to know they can pull and instance container images. Docker and containerD are not intended to pull and instance Helm Charts, Singularity, OPA or other artifact types.
A registry, or container registry, is an instance of the distribution-spec. See Implementers for a list of registries that support OCI Artifacts.
Types that many to most registry operators would likely want to support (OCI Image, Helm, Singularity). While registry operators are not required to support all types, registry operators would likely want to support well known types, if there was an easy way to understand the differing types. OCI Artifacts includes publishing of well-known types for registry operators to import.
OCI Artifacts provides an alternative to having to build, distribute and run "Yet Another Storage Service".