Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deleting images with v2 does not work, wrong digest #1637

Closed
EugenMayer opened this issue Apr 15, 2016 · 4 comments
Closed

Deleting images with v2 does not work, wrong digest #1637

EugenMayer opened this issue Apr 15, 2016 · 4 comments

Comments

@EugenMayer
Copy link

Finally go teached about storage->delete->true in the configuration https://github.com/docker/distribution/blob/master/docs/configuration.md

and implemented it. Still, while fetching the digest https://github.com/EugenMayer/docker_registry_cli/blob/master/DockerRegistryRequest.rb#L92 getting a string like sha256:XXXX

Using this to feed into delete https://github.com/EugenMayer/docker_registry_cli/blob/master/DockerRegistryRequest.rb#L83
i get notfied, that the digest is wrong.

Using the current latest registry:2 (sha256:20f5d95004b71fe14dbe7468eff33f18ee7fa52502423c5d107d4fb0abb05c1d).

Is this a bug / fixed already?

@EugenMayer
Copy link
Author

@RichardScothern
Copy link
Contributor

docker/docker-registry is a different repository and product.

Please read the spec about deleting manifests:
https://github.com/docker/distribution/blob/master/docs/spec/api.md#deleting-an-image

@stonelion
Copy link

@EugenMayer using this:
curl -I -H Accept:application/vnd.docker.distribution.manifest.v2+json will get correct digest

@EugenMayer
Copy link
Author

thank you @stonelion worked out settings this header and yes, its in the docs, but its neither convinient nor obvious to see. For a rest-API the docs are very unstructured ;/

Any thank you

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

No branches or pull requests

3 participants