Skip to Content
Operation Guide

Operation Guide

1. Creation and Deletion

1.1 Create an Image Repository

On the UHub (image repository) product page, click Create Image Repository, enter the image repository name and remarks to complete the creation. If the current project already has image repositories, select Create a New Image Repository from the drop-down list of repository names.

  • The image repository name must be globally unique (cannot overlap with names used by other users or projects).
  • Each project supports a maximum of 8 image repositories.

1.2 Delete an Image Repository

Click the Delete Image Repository button in the upper-right corner of the image repository console page to delete the repository.

  • Only empty image repositories can be deleted. If the repository still contains images, delete them first.

2. Accounts and Permissions

Environmental Preparation: Log in via docker login on a machine with Docker (version 1.10 or higher) installed.

2.1 Console Account

The login username is the email registered on the ZOSOC platform, and the password is your console login password.

Login into the image repository via Docker command and access the service via domain name:

docker login uhub.zosoc.com -u {user@email}

2.2 Independent Password

You can set an independent password on the Container Image Repository page. The account for the independent password is the email registered on the ZOSOC platform, and the password is the one you set.

  • If the independent password differs from the console login password, both can be used.
  • The independent password is bound to the login username, not to specific image repositories.
  • Modifying the independent password affects all image repositories and supports login via both ZOSOC’s internal network and public network.

3. Repository Access Settings

Externally shared image repository

By default, image repositories are private and can only be pulled by the primary account and sub-accounts with appropriate permissions for the project containing the repository.

If you want your images to be pulled by other users on the platform, you can set the externally shared image repository to public.

External Network Access

You can disable pushing and pulling images via the public network using the External Network Access toggle.

If your repository is configured as a publicly shared image repository, only public network pushes will be prohibited, while public network pulls will still be allowed.

4. Push and Pull Images

4.1 Push Images

Step 1: Give a tag to a local image:

docker tag {local image name} uhub.zosoc.com/{created image repository}/{image}:tag

Step2: Push the image to the repository:

docker push uhub.zosoc.com/{created image repository}/{image}:tag

4.2 Pull Images

docker pull uhub.zosoc.com/{created image repository}/{image}:tag

5. Cross-Region User Experience

The ZOSOC public image repository adopts a cross-region architecture. Images pushed to a node in one region can be pulled via internal network from nodes in other regions.

For example, in North China 1 Availability Zone C, push the image: img
In Shanghai Region 2, pull the image: img

Once the image push is completed, all ZOSOC regions covered by internal networks can pull the pushed images via internal network.

6. Usage Limitations

  1. A single image can retain up to 800 Tags. If exceeding 800 Tags, unused Tags and related images that have not been pulled within one month will be deleted, prioritizing the deletion of earlier uploaded images.
  2. No size limit is imposed on images, but pushing single-layer images exceeding 5G may fail.
  3. External network image pulling speed is limited to 1MB/s per layer.
  4. Regions currently unsupported for internal network image pulling: Fujian.
OverviewFAQ