# Container Registry

Container Registry (SCR) stores and distributes private OCI images within a Project. It gives Build outputs and other container images a named location that authorized tools can push to or pull from.

## Why use Container Registry?

Build systems and runtimes need to exchange the same image. A registry provides that handoff, while image digests let a consumer select exact content and tags provide names that can move as you publish updates.

## What you can do

- Configure Docker to authenticate with your current Account session.
- Push and pull images through the OCI Distribution interface.
- Inspect repositories, image manifests, and tags through the API or CLI.
- Supply private images to Run and Sandbox within the Project.

## Core concepts

A **Repository** is a named image collection, created on the first authorized push. An **Image** is an immutable manifest, index, or artifact identified by its digest. A **Tag** is a mutable name pointing to one Image.

References include the Account, Project, and repository. Use a digest when the consumer must run an exact image. Registry access requires authorization; images are private.

## Use Container Registry

Read the [CLI reference](/docs/scr/reference/cli) for commands or the [API reference](/docs/scr/reference/api) for resources, request fields, and responses.

## Related services

- [Build](/docs/build)
- [Run](/docs/run)
- [Sandbox](/docs/sandbox)

---

Company: Socra — Multiply Your Judgment
Canonical URL: https://cloud.socra.com/docs/scr