Project

Profile

Help

Send by e-mail

Issue #4646

'docker-content-digest' header is not returned with requests for a tag

Added by dkliban@redhat.com 8 months ago. Updated 5 months ago.

Status:
MODIFIED
Priority:
Normal
Assignee:
ipanova@redhat.com
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Severity:
2. Medium
Version - Docker:
Platform Release:
Blocks Release:
Target Release - Docker:
OS:
Backwards Incompatible:
No
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 55

Description

Crane and Pulp don't set the 'Docker-content-digest' header [0]. Users want to make a HEAD request for a tag to find out if that tag is pointing to a new manifest. Without this header, users must download the manifest in order to learn its digest.

The first thing that I found when searching the web is a bug about Crane1. We need to fix this for Pulp 3.

[0] https://docs.docker.com/registry/spec/api/#content-digests
[1] https://github.com/renovatebot/renovate/issues/2315

Associated revisions

Revision b8cca325 View on GitHub
Added by ipanova@redhat.com 5 months ago

Add 'Docker-Content-Digest' header to the reasponse headers.

closes #4646
https://pulp.plan.io/issues/4646

Revision b8cca325 View on GitHub
Added by ipanova@redhat.com 5 months ago

Add 'Docker-Content-Digest' header to the reasponse headers.

closes #4646
https://pulp.plan.io/issues/4646

History

#1 Updated by amacdona@redhat.com 8 months ago

  • Description updated (diff)

#2 Updated by ipanova@redhat.com 7 months ago

this headers is optional, in addition docs state that you should not rely on this header because it is not trusted

#3 Updated by ipanova@redhat.com 7 months ago

however for compatibility of clients it is better to include the header whenever the digest is available.

#4 Updated by dkliban@redhat.com 7 months ago

  • Triaged changed from No to Yes

#5 Updated by bmbouter 7 months ago

  • Tags deleted (Pulp 3)

#6 Updated by ipanova@redhat.com 5 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ipanova@redhat.com

#7 Updated by ipanova@redhat.com 5 months ago

  • Status changed from ASSIGNED to POST
  • Sprint set to Sprint 55

#8 Updated by ipanova@redhat.com 5 months ago

  • Status changed from POST to MODIFIED

Please register to edit this issue

Send by e-mail

Also available in: Atom PDF