Container registries, implementing the distribution-spec, provide reliable, highly scalable, secured storage services for container images. Customers either use a cloud provider implementation, vendor implementations, or instance the open source implementation of distribution. They configure security and networking to assure the images in the registry are locked down and accessible by the resources required. Cloud providers and vendors often provide additional values atop their registry implementations from security to productivity features.
Applications and services typically require additional artifacts to deploy and manage, including helm for deployment and Open Policy Agent (OPA) for policy enforcement.
Utilizing the manifest and index definitions, new artifacts, such as the Singularity project, can be stored and served using the distribution-spec.
This repository provides a reference for artifact authors and registry implementors for supporting new artifact types with the existing implementations of distribution.
By providing an OCI artifact definition, the community can continue to innovate, focusing on new artifact types without having to build yet another storage solution (YASS).
- The Apache License, Version 2.0
- Maintainers
- Maintainer guidelines
- Contributor guidelines
- Project governance
- Release procedures
This project incorporates (by reference) the OCI Code of Conduct.
This project incorporates the Governance and Releases processes from the OCI project template: https://github.com/opencontainers/project-template.
This project would continue to use existing channels in use by the OCI developer community for communication
Artifacts will reference specific distribution, index and manifest versions in its examples, identifying any dependencies required.
Q: Does this change the OCI Charter or Scope Table?
A: No. Artifacts are a prescriptive means of storing index and manifest within distribution implementations.