Help Center/ SoftWare Repository for Container/ User Guide (Enterprise Edition)/ Image Management/ Image Management Overview
Updated on 2025-09-19 GMT+08:00
View PDF
Share

Image Management Overview

SoftWare Repository for Container (SWR) provides easy, secure, and reliable management of container images throughout their lifecycle, facilitating the deployment of containerized applications. You can purchase image repositories of different specifications as needed.

  • Pushing images: Pushing images (also called uploading images) helps you push local images to an SWR image repository, so that you can manage images more conveniently. You can use either a container engine client or the SWR console to push your images. Currently, there are two types of container engine clients: Docker and containerd. The supported image artifact types are Docker Image Manifest V2 Schema 2 and Open Container Initiative (OCI).
  • Pulling images: Pulling images (also called downloading images) is the process of obtaining images from an image repository. Then, you can use this image to deploy containerized applications in CCE or CCI.
  • Adding image triggers: SWR often works with CCE or CCI to enable automatic application updates. You can add a trigger to automatically update the application that uses the image when the image tag is updated.
  • Replicating images: After images are uploaded, you can synchronize images of the latest tags to the image repository in another region. Both manual replication and automatic replication are supported.
  • Managing image tag immutability: To ensure end-to-end trustworthiness and prevent existing images from being overwritten after access credentials are leaked, SWR provides image tag immutability. You can create image tag immutability policies for images in a namespace to ensure that image tags will not be overwritten.
  • Image signing and verification: To ensure image consistency during distribution and deployment and prevent man-in-the-middle attacks, unauthorized image updates, and unauthorized images, SWR provides the image signing function. After an image is uploaded, it is automatically signed based on the signing rules. When services such as CCE use the image to deploy applications, the image is verified to ensure security.
  • Adding image retention policies: After images are pushed, you can add retention policies to automatically delete any unused images. There are policies based on the number of image retention days and policies based on the number of image tags.
Parent topic: Image Management