Skip to content
This repository has been archived by the owner on Sep 12, 2018. It is now read-only.

Push Manifest by http api v2 failed #1097

Open
icedir opened this issue Feb 19, 2017 · 0 comments
Open

Push Manifest by http api v2 failed #1097

icedir opened this issue Feb 19, 2017 · 0 comments

Comments

@icedir
Copy link

icedir commented Feb 19, 2017

When i push a images by http api v2 ,i failed.
I obey the https://docs.docker.com/registry/spec/api/

Anyone help me to know what's i'm wrong?
This is my process order:

  1. POST /v2/<name>/blobs/uploads/ > get uuid and Location
  2. RUN linux shell docker save <image> >get a tarfile of my image
  3. RUN linux shell sha256sum tarfile >get my tarfile digest
  4. PUT /v2/<name>/blobs/uploads/<uuid>?digest=<digest> >use step 3 generated digest upload
    i use curl -T tarfile -X PUT /v2/<name>/blobs/uploads/<uuid>?digest=<digest>
  5. PUT /v2/<name>/manifests/<reference> >get a ERROR ,MANIFEST_INVALID manifest invalid,but i look the registry file system,my image was upload success only not has a manifest in the folder named _manifest

My question:
when i upload a new image to registry ,where can i get the right manifest content?

PS:My english is not good,thx for your read

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant