What is Artifact Registry?
Store container images and deploy them in your RDC Cloud project.
Artifact Registry stores container images for a project. Browse repositories and image versions in the Console, push and pull images with Docker, and select stored images when creating a Container Engine resource.
Repositories, tags, and digests
A repository groups versions of an image. A tag is a readable version label; a digest identifies specific image content. Open Artifact Registry to see the repository list and image counts. Select a repository to open its Overview image table. Use the sidebar to switch sections and Back to list to return to repositories. Each row shows tags and a digest, size, push time, and a button to copy the digest-qualified image reference. Use the controls below the table to move between image pages.
Use the registry address shown in the selected project rather than guessing a path from its display name. Credentials use a personal access token, and access follows the user's current project permissions.
Get started
Authenticate Docker, push and pull an image, then deploy it with Container Engine.
Delete a repository
Open the repository, select Danger Zone in the sidebar, then click Delete repository. Enter the exact repository name and confirm. Deletion permanently removes all images and tags in that repository. Running containers are not deleted, but later pulls, deployments or restarts that need these images may fail. This action cannot be undone.
Deletion requires artifact_registry.repositories.delete, included in the Artifact Registry Admin, Admin and Owner roles. Read or push access alone does not permit deletion. If a registry policy prevents deletion or a request fails, the confirmation remains available for an explicit retry. The Console returns to the repository list after success.
Image-level deletion and retention-policy controls are not exposed.
Passkey confirmation for deletion
If your account has a registered passkey, deleting this cloud resource requires a new passkey verification, even if you already verified your sign-in. After confirming deletion in Console, use Verify with passkey in the RDC Account window. Allow pop-ups for Console if the verification window is blocked.
The verification applies only to the selected resource and one deletion attempt. Cancelling, closing the window, or letting the request expire does not send the deletion request. If deletion fails, start a new attempt and verify again. Accounts without a registered passkey continue to use the existing deletion confirmation. Your resource deletion permission is still required.
Product navigation
The sidebar keeps Getting started and the resource list available. Opening the product first checks the selected project. A successful, complete empty result opens Getting started; existing resources open the list. Errors and loading states stay in place. Selecting the list explicitly keeps it open even when it is empty.
Lists and resource details use the available workspace width. Getting started links to the existing creation or management flow and documentation; existing permissions still apply.