Skip to content
Branch: master
Clone or download
Latest commit de2d822 Sep 4, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.pullapprove.yml Fix up PullApprove config Aug 29, 2019
CONTRIBUTING.md Initial commit Aug 16, 2019
GOVERNANCE.md Initial commit Aug 16, 2019
LICENSE Initial commit Aug 16, 2019
MAINTAINERS
MAINTAINERS_GUIDE.md Initial commit Aug 16, 2019
README.md add more context to readme Aug 30, 2019
RELEASES.md Initial commit Aug 16, 2019
definitions-terms.md Add definitions and terms Aug 29, 2019

README.md

OCI Artifacts

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. More particularly this repository has been tasked by the OCI TOB to serve 3 primary goals:

  1. artifact authors - guidance for authoring new artifact types. Including a clearing house for well known artifact types.
  2. registry operators and vendors - guidance for how operators and vendors can support new artifact types, including how they can opt-in or out of well known artifact types. Registry operators that already implement media-type filtering will not have to change. The artifact repo will provide context on how new media-types can be used, and how media-types can be associated with a type of artifact.
  3. clearing house for well known artifacts - artifact authors can submit their artifact definitions, providing registry operators a list by which they can easily support.

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).

Table of Contents

Code of Conduct

This project incorporates (by reference) the OCI Code of Conduct.

Governance and Releases

This project incorporates the Governance and Releases processes from the OCI project template: https://github.com/opencontainers/project-template.

Project Communications

This project would continue to use existing channels in use by the OCI developer community for communication

Versioning / Roadmap

Artifacts will reference specific distribution, index and manifest versions in its examples, identifying any dependencies required.

Frequently Asked Questions (FAQ)

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.

You can’t perform that action at this time.