Closed EugenMayer closed 8 years ago
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?
i am not alone here, seems its a general issue https://github.com/docker/docker-registry/issues/988#issuecomment-210190903
dupe, using https://github.com/docker/distribution/issues/1637
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?