# What is Container registry?

A private OCI registry for your organization, used with docker, helm, oras, cosign and notation, with vulnerability scans, signatures, lifecycle rules and storage quotas.

Your organization has one registry host, `<organization>.ecr.<platform domain>`. Every repository
lives under it, and any OCI client works against it: `docker push` and `docker pull`, `helm push`,
`oras`, `crane`, `cosign` and `notation`. A repository is private unless you make it public.

## When to use it

- Store the images your apps, functions and Kubernetes clusters run, next to them.
- Mirror Docker Hub, GitHub Container Registry and other public registries, so CI does not depend
  on their rate limits (see [Use a pull-through cache](use-a-pull-through-cache.md)).
- Deploy only images a key you trust has signed (see
  [Only deploy signed images](only-deploy-signed-images.md)).

## Concepts

| Term                 | Meaning                                                                                                                 |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Registry**         | One host per organization, `<organization>.ecr.<platform domain>`.                                                      |
| **Repository**       | A named collection of images, addressed as `<host>/<repository>`. Names may nest: `team/api`, `charts/web`.             |
| **Visibility**       | `private`: every pull needs credentials. `public`: anyone can pull the repository's own images without credentials.     |
| **Tag**              | A name for one image, as in `<host>/my-app:v1.2.0`. Pushing again moves it, unless the repository's tags are immutable. |
| **Digest**           | An image's fixed identity, `sha256:…`. Pull `<host>/my-app@sha256:…` to get exactly that image.                         |
| **Login token**      | A password for `docker login` that works for 12 hours.                                                                  |
| **Scan**             | A Trivy run over one image, with counts per severity and the list of findings.                                          |
| **Referrer**         | An artifact about an image (a signature, an SBOM, an attestation) linked to it by its `subject` (OCI 1.1).              |
| **Lifecycle policy** | Rules applied every hour that delete images; a deleted image stays restorable for a number of days, then it is purged.  |

See [Repositories, tags and images](repositories-and-images.md),
[Lifecycle policies](lifecycle-policies.md) and [Storage and cleanup](storage-and-cleanup.md).

## Pricing

You pay for stored image layers per GB-month. Each layer counts once, however many repositories
or tags share it. Layers held only by images a lifecycle rule deleted count until they are purged;
layers no image uses any more do not count. See [Storage and cleanup](storage-and-cleanup.md).

## Interfaces

- The Deutsche Cloud Console: **Container registry** lists your repositories (**Image repositories**) and the
  registry settings **Access**, **Pull-through cache**, **Signing**, **Storage** and
  **Lifecycle defaults**.
- Any OCI client, against your registry host.
- The `dcloud ecr` commands, the API under `/ecr/api`, and Terraform (`dcloud_ecr_*`).

## Next steps

- [Getting started](getting-started.md)
- [Create a repository](create-a-repository.md)
- [Log in to the registry](log-in.md)
