Repositories

Managing Container Registry repositories

Repositories appear in the console and API after the first push to a namespace. The API exposes metadata including tags, artifacts, sizes, and last push/pull times.

Repository lifecycle

First push to namespace/repository → Repository created automatically
        │
        ├─ Subsequent pushes add tags and artifacts
        │
        ├─ Delete artifact → Remove single digest (and its tags)
        │
        └─ Delete repository → Remove all tags and artifacts

You cannot create repositories manually. Push an image to {namespace}/{repository-name} and the repository is provisioned on first upload.

Available operations

Action	Description
List repositories	All repositories in a namespace
Get repository	Tags, artifacts, digests, and size breakdown
Delete repository	Removes the repository and all tags and artifacts
Delete artifact	Remove a single digest (and its tags) via `DELETE …/delete-request?digest=sha256:…`

Metadata

Repository listings and detail views include:

Field	Description
Tags	Mutable labels pointing at artifacts (for example `v1.2.0`, `latest`)
Artifacts	Immutable manifests identified by digest
Size	Stored size per artifact and repository total
Last push / pull	Timestamps from usage events recorded by the platform

Deleting artifacts

To remove a single digest without deleting the entire repository:

DELETE …/delete-request?digest=sha256:…

This removes the artifact and any tags that reference it. Other artifacts and tags in the repository are unaffected.

Deleting repositories

Deleting a repository removes all tags and artifacts within it. This action is irreversible and reduces stored size (and ongoing storage charges) for that repository.

Deleting namespaces

Deleting a namespace removes the namespace record and stops billing for that namespace. Underlying registry storage is cleaned up asynchronously. All repositories within the namespace are removed as part of this process.