📄️ Authentication
There are two ways we will be covering in this guide to authenticate with OCI Registries.
📄️ Pushing and Pulling
All users can access container images stored in centralized repositories called OCI registries. Pushing OCI artifacts to the registries is the first step in distributing them. These artifacts can be pulled by other people and used in their own environment once they have been stored.
📄️ Manifest Config
According to OCI Image Manifest Specification,
📄️ Manifest Annotations
Annotations, which are supported by OCI Image Manifest and OCI Content Descriptors, are also supported by oras.
📄️ Distributing OCI Layouts
The directory structure for OCI content-addressable blobs and location-addressable references (refs) is called the OCI Image Layout. An OCI Image needs to include:
📄️ Distributing Artifacts with Remote Registries
Remote OCI registries allow you to share container images and other artifacts.
📄️ Validating ORAS CLI Binaries
After finding your target release,
📄️ Backup and Restore of OCI Artifacts, Images, and Repositories
Overview
📄️ Go Scripting
It is possible to use the ORAS CLI in Go scripts.
📄️ Formatted output
The ORAS command allows users to format the metadata output and perform computations on data based on the formatted output. The ORAS command also allows the --output option to write to a file or directory.
📄️ Create and Manage Multi-architecture Artifacts
ORAS can help you create and manage multi-architecture artifacts such as configurations, executables, and container images.
