failed to read expected number of bytes: unexpected EOF

[yulinor]

Description

Registry as a pull through cache，after node A completes the image pull, node B pulls and reports the following error:
E0612 14:14:38.404593 398678 remote_image.go:167] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image <app_a_image:v10>: failed to read expected number of bytes: unexpected EOF" image=
FATA[0001] pulling image: rpc error: code = Unknown desc = failed to pull and unpack image <app_a_image:v10> : failed to read expected number of bytes: unexpected EOF

Pulling other version images of app_a also reports an error.Pulling app_b image is normal.

The debug log is not enabled. After restarting the service in debug mode, it pulls normally but fails to reproduce.

Registry works in memory not redis. Is this a problem?

Reproduce

dont know..

Expected behavior

No response

registry version

2.8.3

Additional Info

No response

[milosgajdos]

Can you please format your log output.

Would you mind testing this on the v3 alpha release. I'd strongly recommend against using v2.x releases.

[yulinor]

Can you please format your log output.

Would you mind testing this on the v3 alpha release. I'd strongly recommend against using v2.x releases.

The logs that trigger the image pull are in the following form:

172.31.16.10 - - [12/Jun/2024:09:45:44 +0000] "GET /v2/xxxx/blobs/sha256:xxx?ns=xxx HTTP/1.1" 200 7060 "" "containerd/v1.6.23"

INFO[12529] response completed                            go.version=go1.20.8 http.request.host="" http.request.id=07704185-422d-4b1b-afa2-e65712ba9fc8 http.request.method=GET http.request.remoteaddr="" http.request.uri="/v2/xxxx/blobs/sha256:xxxx?ns=xxxx" http.request.useragent="containerd/v1.6.23" http.response.contenttype="application/octet-stream" http.response.duration=970.833235ms http.response.status=200 http.response.written=212596670

v3 does not have a stable version and is inconvenient to go online

[milosgajdos]

v3 does not have a stable version and is inconvenient to go online

This is a fair point but beware there hasn't been any updated made in v2 and will not be other than security updates.

So if there is some bug, I'm afraid we won't fix it. You'll have to wait for v3 release.