What Should I Do If Docker Client Fails to Push Images?
Symptom
The logged-in Docker client is used to upload an image package. For example, the following command is executed:
docker push xxx/test/busybox:latest
- xxx indicates the address of the repository to which the tenant or user is to upload the image.
- test indicates the organization.
- busybox is the image name.
- latest indicates the latest image version.
However, the upload fails, and the following information is displayed on the Docker client:
unauthorized: authentication required
Solution
- On the SWR page, choose My Images > Upload Through Docker Client > Generate a temporary Docker login command, and copy the command.
- Click Organization Management and create an organization, for example, test.
- Log in to a data plane node and run the command obtained in 1.
- Run the following command to upload an image to an organization on which the current tenant or user has the operation permission. For example, upload an image named busybox to the organization test created in 2.
docker push xxx/test/busybox:latest
- xxx indicates the address of the repository to which the tenant or user is to upload the image. It is the tail of the command copied in 1, for example, swr.{regionID}.{external_global_domain_name}.
- test is the organization on which the tenant or user has the operation permission.
- latest indicates the latest image version.
- After the image is uploaded, the following information is displayed.
The push refers to a repository [xxx/test/busybox] 6a749002dd6a: Pushed latest: digest: sha256:ecb3f3e96e003af6e02f0f47ac4d25a3b0585db54de0a82bb070f8cb78a79bc7 size: 527
If an exception occurs, contact technical support.
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