support global request_timeout_sec by wswsmao · Pull Request #2215 · containerd/stargz-snapshotter (original) (raw)
Conversation
This PR adds a global request_timeout_sec field to the [resolver] configuration, allowing users to override the 30s hardcoded default for all registry requests at once and preventing context deadline exceeded errors during large layer prefetching.
support global request_timeout_sec to override hardcoded 30s default support global request_timeout_sec
Comment on lines +233 to +234
| You can also configure mirrored registries, insecure connection and request timeout. |
|---|
| The global `request_timeout_sec` field under `[resolver]` sets the default timeout (in seconds) for each request to the registry. If not specified, the default value is 30 seconds. |
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you separate this part to a separated section or move it at the end of this section?
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
Signed-off-by: abushwang abushwang@tencent.com
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})
2 participants
