A repository is a collection of images. We recommend that you place all image tags of an application or a feature in the same repository. This topic describes the main features of a repository.
Repository naming
We recommend that you use the name of a software package or an application as the name of a repository.
- Example of using the software package name as the name of a repository: centos or jetty
- Example of using the application name as the name of a repository: console-web or console-service
Main features of a repository
- Configure repository visibility
- If you configure a public repository, all users can pull images from it anonymously.
- If you configure a private repository, only authorized users can pull images from it after logon.
- Deploy images
On the details page of a repository, click Deploy Application in the upper-right corner. In the dialog box that appears, click Deploy. The specified images in the repository are deployed in the Container Service console.
- Query images
- Query images in a repository and obtain the
Digest
andImageId
values of each image. - Check the image layer information, including the size and metadata for each layer of the images.
- Scan the images to identify vulnerabilities in them and provide solutions for some vulnerabilities.
- Query images in a repository and obtain the
- Set webhooks
- Enable the system to send webhook notifications to the specified webhook URL after images are pushed to a repository.
- Integrate with the downstream processes of Container Registry.
- Authorize a repository
Grant the access permissions on a repository to Resource Access Management (RAM) users.
- Build images
- Manage your source code repositories. After you commit the code, images are built based on the build rules you specify and then pushed to the specified repository.
- Integrate with the upstream processes of Container Registry.