Skip to content

Mismatched content digest when schema 1 conversion is done #1444

@dmcgowan

Description

@dmcgowan

When schema2 is pushed with 1.10 then a pull is done from 1.6.x or 1.7.x, the DOCKER-CONTENT-DIGEST header verified to match the manifest content. Currently this value is not updated on schema1 conversion sending the digest of the schema2 manifest.

The error in Docker 1.7.1 looks like

ERRO[0005] Error from V2 registry: error verifying manifest: unable to verify manifest digest: registry has "sha256:fea8895f450959fa676bcc1df0611ea93823a735a01205fd8622846041d0c7cf", computed "sha256:d7c4d57978f00c73a82f334c48043f0c0cb049ebb91c85fa560b88ba79ad6e8d"

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions