- What's new
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- Introduction
- Permissions Management
- Basics of the Container Engine
-
Image Management
- Uploading an Image Through a Container Engine Client (Recommended)
- Obtaining a Long-Term Valid Login Command
- Uploading an Image Through SWR Console
- Pulling an Image
- Setting Image Attributes
- Sharing a Private Image
- Adding a Trigger
- Adding an Image Retention Policy
- Configuring Automatic Image Synchronization Between Regions
- Image Center
- Organization Management
- User Permissions
- Auditing
- Change History
- Best Practices
-
API Reference
- Before You Start
- Calling APIs
- API Overview
-
API
- Organization Management
- Managing Image Repositories
- Image Tag Management
- Shared Account Management
- API Version
- Organization Permission Management
- Image Permission Management
- Image Synchronization Management
- Trigger Management
- Image Retention Policy Management
- Temporary Login Command
- Quota Management
- Other
- Example Applications
- Appendixes
- SDK Reference
-
FAQs
- General FAQs
- Login Issues
- Synchronizing Images
- Pushing an Image
- Pulling an Image
-
Troubleshooting
- Why Does the Login Command Fail to Be Executed?
- Why Does an Image Fail to Be Pushed Through a Container Engine Client?
- Why Does an Image Fail to Be Uploaded Through SWR Console?
- Why Does the docker pull Command Fail to Be Executed?
- What Should I Do If Images Cannot Be Downloaded from Private Networks?
- What Do I Do If an Error Occurs When I Call an API?
-
Other FAQs
- Why Does a CCE Workload Cannot Pull an Image from SWR and a Message "Not Logged In" Is Displayed?
- How Many Tenants Can I Share an SWR Private Image With?
- Why Is an Image Pushed Using a Container Engine Client to SWR Different in Size From One Uploaded Through the SWR Console?
- Can I Pull Images on the SWR Console to a Local PC?
- Videos
- Glossary
-
More Documents
- User Guide
- API Reference
- User Guide (Paris Regions)
- API Reference (Paris Regions)
- User Guide (Kuala Lumpur Region)
- API Reference (Kuala Lumpur Region)
-
User Guide (Ankara Region)
- Service Overview
- 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
- Organization Management
- User Permissions
- FAQs
-
API Reference (Ankara Region)
- Before You Start
- API Overview
- Calling APIs
- API
- Appendixes
- Permissions and Supported Actions
- General Reference
Copied.
Why Does an Image Fail to Be Uploaded Through SWR Console?
SWR has strict requirements on image name and address format. Invalid image names or addresses could lead to upload failures.
Invalid Image Format
Problem: When you upload an image to SWR through the SWR console, an error message is displayed, indicating that the image format is invalid.
Possible cause: Invalid image address leads to upload failure.
The image tag, which is at the end of an image address, can be omitted. When it is omitted, the latest version of the image will be pushed. Other parts of the image address cannot be omitted. Ensure that they are all correctly configured.
Example: registry.example.com/repo_namespace/repo_name:tag
- registry.example.com is an example address of the SWR image repository. Replace it with the actual address.
- repo_namespace: organization name. It contains a maximum of 64 characters and must meet regular expression ^([a-z]+(?:(?:(?:_|__|[-]*)[a-z0-9]+)+)?)$.
- repo_name:tag: image name and tag. The image name contains a maximum of 128 characters and must meet regular expression ^([a-z0-9]+(?:(?:(?:_|__|[-]*)[a-z0-9]+)+)?)$.
To view the image address, decompress the image. Open the manifest.json file, and check the value of RepoTags.
![Click to enlarge](https://support.huaweicloud.com/intl/en-us/ae-ad-1-usermanual-swr/en-us_image_0000001127162558.png)
Solution: Tag the image again according to the naming rules. Run the docker save command, and upload the image on the SWR console.
Stuck at the Upload Page Until It Times Out
Problem: When you upload an image to SWR through the SWR console, the upload progress is stuck and the upload task times out at the end.
Possible cause: Invalid image name leads to upload failures.
Solution: Modify the image name according to the naming rules, and try uploading the image again.
It is the image name in the repositories and manifest.json files that should be checked and modified rather than the name of the image file you select and upload on the SWR console.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot