All Products
Search
Document Center

Container Registry:Main features of a repository

Last Updated:Mar 26, 2026

A repository stores, manages, and distributes container images for a single application across multiple versions. It supports version control, permission control, automatic integration, and security management. Store all versions of an application's images in one repository to keep them organized and easy to manage.

Repository naming

Use the name of a software package or application as the repository name:

  • Software package name: centos or jetty

  • Application name: console-web or console-service

Repository features

Visibility settings

Control who can pull images from your repository:

VisibilityAccess behaviorTypical use case
PublicAny user can pull images anonymously.Open-source software, publicly distributed images
PrivateOnly authorized users can pull images after logging on.Proprietary or sensitive application images

Set visibility when you create the repository or update it at any time from the repository settings page.

Authorization

Grant Resource Access Management (RAM) users access permissions on a specific repository.

Image query

Inspect the contents of a repository to understand what is stored:

  • Query images and retrieve the Digest and ImageId values for each image.

  • View image layer details, including the size and metadata for each layer.

Image-based deployment

Deploy images directly from a repository to Container Service for Kubernetes. On the repository details page, click Deploy Application, then click Deploy in the dialog box. The specified images in the repository are deployed in the Container Service for Kubernetes console.

Webhook

Automate downstream workflows when images are pushed to a repository:

  • Send webhook notifications to a specified URL after each image push.

  • Integrate with downstream processes in Container Registry.

Image building

Automate image creation from source code to reduce manual build steps:

  • Manage source code repositories and define build rules. When code is committed, Container Registry automatically builds images based on the rules and pushes them to the specified repository.

  • Integrate with upstream processes in Container Registry.