Skip to content

Returning manifest digest fails for registries which don't send Docker-Content-Digest http header #3792

@rsafonseca

Description

@rsafonseca

Not all repositories send "Docker-Content-Digest" header in their HTTP responses to manifest fetches.
Most notably, AWS ECR is affected by this problem, and quite possibly there's a few other registries out there with similar implementation issues.
This results in manifests.Get(...) method of the registry client (registry/client/repository.go) to not return the digest when contentDigestOption is set for the affected registries.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions