Content length issue with Docker Hub proxy cache and Containerd #19728
Unanswered
elchenberg
asked this question in
Q&A
Replies: 1 comment
-
It probably relates to this issue. #19429 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have an issue with my Harbor proxy cache and containerd.
Containerd seems to send a HEAD request to Harbor to get the digest and size of a tag manifest (
request.method=HEAD url="https://my-registry-host.tld/v2/docker-hub/library/busybox/manifests/latest?ns=docker.io"
).Harbor responds with (among others) a content-length and a docker-content-digest:
response.header.content-length=2295 response.header.docker-content-digest="sha256:5c63a9b46e7139d2d5841462859edcbbf57f238af891b6096578e5894cfe5ae2"
).Containerd then GETs the manifest using the digest (
request.method=GET url="https://my-registry-host.tld/v2/docker-hub/library/busybox/manifests/sha256:5c63a9b46e7139d2d5841462859edcbbf57f238af891b6096578e5894cfe5ae2?ns=docker.io"
) and it expects the size to be 2295.But Harbor now reports a different content-length (
response.header.content-length=9517 response.header.docker-content-digest="sha256:5c63a9b46e7139d2d5841462859edcbbf57f238af891b6096578e5894cfe5ae2"
) and containerd'ssize validation
fails.I am not sure if there is something wrong with Harbor or with containerd. Is the content length in the first Harbor response wrong/outdated?
Harbor version: v2.9.1-5cbb1b01
Containerd version: 1.6.21 66c1fbccbaaac631b77184b7957e67fea4cf45ab
Containerd debug log:
Beta Was this translation helpful? Give feedback.
All reactions