Skip to main content
Create a repository in your selected account and region, then use its returned uri to push and pull images.

​
Log in

Exchange your platform token for a registry credential. Keep its password out of shell arguments and logs; use your client’s standard input option.
The response includes the credential’s expires_at. Renew it when it expires. The client obtains separate repository-scoped bearer tokens during push and pull. Those access tokens last five minutes; policy revocations apply when access is evaluated for the next token.

​
Push a release

Set IMAGE_URI to the returned repository URI and push your local image:
For reproducible deployments, use IMAGE_URI@sha256:... with the digest returned by the push. A tag is convenient for discovery; a digest identifies the exact manifest. The parsed manifest in a REST response is for inspection. Retrieve the original manifest through your OCI client when verifying its digest.

​
Inspect and remove

List images under /v1/repositories/{repository_id}/images, and tags under /v1/repositories/{repository_id}/tags. The image list accepts tag_status and tag_prefix; tag pagination uses a tag name as its cursor. Batch deletion accepts explicit digest or tag entries. Inspect each result: one failed entry does not make all other entries fail. Deleting a nonempty repository requires force=true; that option never overrides deletion protection. Disable protection explicitly before deleting the repository.