-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Ensure errContentRangeIgnored error when range-get request is ignored #12291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
/test pull-containerd-node-e2e |
395d794 to
53d3bad
Compare
… by registry Signed-off-by: Henry Wang <henwang@amazon.com>
53d3bad to
635907e
Compare
|
/cherry-pick release/2.1 |
|
@AkihiroSuda: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@AkihiroSuda: new pull request created: #12312 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
…quest is ignored This patch addresses an issue where containerd was not properly returning the errContentRangeIgnored error when range-get requests are ignored by the registry or storage backend using the new image transfer service. The fix ensures that the appropriate error is returned to maintain consistent error handling behavior for range requests that cannot be processed. Based on upstream PR: containerd/containerd#12291 Signed-off-by: Kyle Sessions <kssessio@amazon.com>
…quest is ignored This patch addresses an issue where containerd was not properly returning the errContentRangeIgnored error when range-get requests are ignored by the registry or storage backend using the new image transfer service. The fix ensures that the appropriate error is returned to maintain consistent error handling behavior for range requests that cannot be processed. Based on upstream PR: containerd/containerd#12291 Signed-off-by: Kyle Sessions <kssessio@amazon.com>
This patch addresses an issue where containerd was not properly returning the errContentRangeIgnored error when range-get requests are ignored by the registry or storage backend using the new image transfer service. The fix ensures that the appropriate error is returned to maintain consistent error handling behavior for range requests that cannot be processed. Based on upstream PR: containerd/containerd#12291 Signed-off-by: Kyle Sessions <kssessio@amazon.com>
Fixed an issue where pulling image fails when
concurrent_layer_fetch_bufferis small.Repro steps:
Here is the dump of the HTTP response, the registry did not return
content-rangein the response header:Fix
The Fetcher sets the
Rangeheader ifparallelism > 1oroffset > 0.containerd/core/remotes/docker/fetcher.go
Lines 455 to 457 in 1843b23
But
withOffsetCheckreturnsnilfor error whenoffset == 0only.containerd/core/remotes/docker/resolver.go
Lines 664 to 666 in 1843b23
This logic cannot handle the scenario when a registry ignores the range-get request for small layers. The correct logic should return
errContentRangeIgnoredin this case.