SoftWare Repository for Container
SoftWare Repository for Container
- What's New
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- Overview
- Permissions Management
- Basics of Docker
-
Image Management
- Pushing an Image Through a Container Engine Client
- Obtaining a Long-Term Valid Docker Login Command
- Obtaining a Long-Term Valid containerd Pull/Push Command
- Uploading an Image Through the SWR Console
- Pulling an Image
- Setting Image Attributes
- Sharing Private Images
- Adding a Trigger
- Adding an Image Retention Policy
- Image Center
- Organization Management
- User Permissions
- Auditing
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
- Organization Management
- Image Repository Management
- Image Tag Management
- Shared Account Management
- API Versions
- Organization Permission Management
- Image Permission Management
- Automatic Image Synchronization Task Management
- Trigger Management
- Image Retention Policy Management
- Temporary Login Command
- Quota Management
- Example Applications
- Appendixes
- Change History
- FAQs
- Videos
- SDK Reference
Help Center/
SoftWare Repository for Container/
User Guide/
Image Management/
Obtaining a Long-Term Valid containerd Pull/Push Command
Obtaining a Long-Term Valid containerd Pull/Push Command
Updated on 2024-11-08 GMT+08:00
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
- Obtain the programmatic access permission by referring to Step 1.
- Obtain the resource space name, image repository address, AK, and login key by referring to Step 2 to Step 4.
- 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 Step 2, the AK in Step 3, and the login key in Step 4.
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 Step 2, the AK in Step 3, and the login key in Step 4.
NOTE:
- 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
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.