Error "Manifest does not match provided manifest digest" when using @sha256:digest in docker-daemon #1051
Labels
kind/bug
A defect in an existing functionality (or a PR fixing it)
locked - please file new issue/PR
stale-issue
When running a
skopeo inspect docker-daemon:repo@sha256:digest
it fails with a "Manifest does not match provided manifest digest" error.After some tests, the cause might be that the contents of the manifest are different (testing with
skopeo inspect --raw
for docker:// source and for docker-daemon: source. My guess in here is that for docker-daemon: source the manifest is automatically generated by Skopeo or the underlying libraries, while for docker:// source, the manifest is downloaded "as is". The docker:// version, when retrieved from the registry, is indented and formatted, so the hash differs with the hash of the locally generated manifest. See my tests:I would expect that it is possible to do a
skopeo inspect docker-daemon:repo@sha256:digest
instead of failing. So some proposals would be:The text was updated successfully, but these errors were encountered: