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
On this page
Image Center
Updated on 2023-12-13 GMT+08:00
Scenario
SWR provides a variety of public images, including official Docker images. You can add official Docker images to My Favorites for ease of use.
Adding an Image to Favorites
- Log in to the SWR console.
- In the navigation pane, choose Image Resources > Image Center.
- In the image list, click
next to an image to add the image to favorites.
You can view all your favorite images on the My Favorites page.
Pulling an Image
You can pull an image without specifying a repository address. For example, you can run the following command to pull the busybox image:
docker pull busybox:latest
Figure 1 busybox image details

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.