docker push docker.art.local/ubuntu

How to troubleshoot Docker problems

AuthorFullName__c
Patrick Russell
articleNumber
000004145
ft:sourceType
Salesforce
FirstPublishedDate
2018-11-13T23:41:06Z
lastModifiedDate
2021-04-23
VersionNumber
7
When a user is ready to push an image, several checks occur before the file is uploaded:

docker push docker.art.local/ubuntu

1. The Docker client will check for the existence of the layers it needs to push:
20180523114900|65|REQUEST|127.0.0.1|admin|HEAD|/api/docker/docker/v2/ubuntu/blobs/sha256:471db38bcfbf0f5bac78012b9d458dfd37309d5cbb99d4e95310321a60a0cfdf|HTTP/1.0|404|0

A 404 not found should be expected at this stage if the layer does not exist in Artifactory yet.

2. The client runs a POST command to submit the blob metadata:
20180523114900|22|REQUEST|127.0.0.1|admin|POST|/api/docker/docker/v2/ubuntu/blobs/uploads/|HTTP/1.0|202|0

3. The client will PATCH the rest of the blob metadata to Artifactory:
20180523114900|60|REQUEST|127.0.0.1|admin|PATCH|/api/docker/docker/v2/ubuntu/blobs/uploads/5582de7a-3127-48d9-bcb5-d61734f14e36|HTTP/1.0|202|0

4. Finally the client sends the layer binary:
20180523114900|122|REQUEST|127.0.0.1|admin|PUT|/api/docker/docker/v2/ubuntu/blobs/uploads/5582de7a-3127-48d9-bcb5-d61734f14e36|HTTP/1.0|201|0

5. Artifactory moves the binaries from a temporary _uploads folder to the Docker image's main location at the base directory of the repository:
 
User-added image