Pushing Docker images

ARTIFACTORY: How to debug docker configuration issues
AuthorFullName__c
Scott Mosher
articleNumber
000005318
ft:sourceType
Salesforce
FirstPublishedDate
2022-06-23T09:15:17Z
lastModifiedDate
2024-03-10T07:44:28Z
VersionNumber
3
For Docker pushes, these requests are not as straightforward. Again, all these requests should be authenticated and will initially be HEAD requests.

|user|HEAD|/api/docker/docker-local/v2/path/some-image/blobs/sha256:be248e90f762e2a43bb52249552e74eceb8e629f1392c664468bf946ea12472c|404|
|user|HEAD|/api/docker/docker-local/v2/path/some-image/blobs/sha256:73dd2a7a91633255c1c8687f3a368b651f6cdc87637e1aa3e6a67ac7868a296b|404|

We then see the POST command uploading to the temporary uploads directory.

|user|POST|/api/docker/docker/v2/path/some-images/blobs/uploads/|202|
|user|POST|/api/docker/docker/v2/path/some-images/blobs/uploads/|202|

The then should see following PATCH and PUT requests for the blobs and the last request would be the manifest/tag.

|user|PATCH|/api/docker/docker-local/v2/path/some-image/blobs/uploads/b3526fec-5803-4733-a1ac-e52e7d09173b|202|
|user|PATCH|/api/docker/docker-local/v2/path/some-image/blobs/uploads/7953cdb7-9a59-4b7e-bab9-fcbde155e972|202|
|user|PUT|/api/docker/docker-local/v2/path/some-image/blobs/uploads/b3526fec-5803-4733-a1ac-e52e7d09173b|201|
|user|PUT|/api/docker/docker-local/v2/path/some-image/blobs/uploads/9ce1ffc5-bf15-4eae-b4dd-2bd030aa8dc6|201|
|user|PUT|/api/docker/docker-local/v2/path/some-image/manifests/latest|201|