yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
1287ab0cee2255cde26ced885dc7b5a9f543e249
doc-exports/docs/swr/umn/swr_01_1001.html
qiujiandong1 1287ab0cee SWR UMN 20250710 version 
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com>
Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com>
Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>
2025-10-29 10:46:14 +00:00

3.9 KiB
Raw Blame History

Obtaining a Long-Term Valid containerd Pull/Push Command

Scenario

This section describes how to obtain a containerd pull/push command that is permanently valid.

  • For security purposes, you are advised to obtain the commands in a development environment.
  • Ensure that you have permission to access the IAM service.

Procedure

  1. Obtain the programmatic access permission by referring to 1.
  2. Obtain the resource space name, image repository address, AK, and login key by referring to 5 to 6.
  3. Concatenate the obtained information to form a long-term valid containerd command.

    1. Image pull command

    ctr image pull --user [Resource space name] @[AK]: [Login key] [Image repository address]

    In the command, the resource space name and image repository address are obtained in 5, the AK in 2, and the login key in 6.

    2. Image push command

    ctr image push --user [Resource space name] @[AK]: [Login key] [Image repository address]

    In the command, the resource space name and image repository address are obtained in 5, the AK in 2, and the login key in 6.

    • The login key is encrypted and cannot be decrypted into an SK.
    • The commands can be executed on other containerd clients to pull and push images.

Parent topic: Image Management