Skip to content

Private container registry quickstart

This quickstart takes one container image from an authenticated push to an authenticated pull. For OCI capabilities and the complete guide map, start with Private container registries.

  1. Create a repository with OCI enabled, or add OCI to an existing repository.
  2. Install Docker or another supported OCI client and sign in to rvs.
  3. Select your repository with rvs art select platform/runtime-images.
  4. Build locally and push an image with rvs docker push acme/api:1.0.0.
  5. Pull it by tag or immutable digest and inspect its graph in Ravenstash.

Docker push, pull, and tag expand short image paths inside the selected repository. Dockerfiles and Buildx output tags still need a full reference. The examples use this readable root:

oci.rvsta.sh/platform/runtime-images

rvs refreshes this root when a namespace or repository is renamed. The image name follows it:

oci.rvsta.sh/platform/runtime-images/acme/api:1.0.0

A tag such as latest, prod, or 1.0.0 is a mutable selector. A manifest digest such as sha256:... is the immutable revision identity.

OCI attachments such as signatures, attestations, SBOMs, and provenance can be stored and discovered as referrers.