-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
nerdctl insecure registry config #8339
Conversation
nerdctl insecure registry config
Hi @mircyb. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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/test-infra repository. |
apply conversations advice
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mircyb Neat 👍
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: floryut, mircyb The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This allow to workaround kubernetes-sigs#8375 by using image_command_tool=crictl when containerd_registries is used for containerd. Also changes image_info_command_on_localhost for docker to return digests. (cherry picked from commit cfd9873) The cherry-pick was adapted because nerdctl_extra_flags is not in the release-2.18 branch (kubernetes-sigs#8339).
This allow to workaround #8375 by using image_command_tool=crictl when containerd_registries is used for containerd. Also changes image_info_command_on_localhost for docker to return digests. (cherry picked from commit cfd9873) The cherry-pick was adapted because nerdctl_extra_flags is not in the release-2.18 branch (#8339).
Backport kubernetes-sigs#8339 to 2.18-release
Backport kubernetes-sigs#8339 to 2.18-release Cherry-pick 24f1402
Backport kubernetes-sigs#8339 to 2.18-release Cherry-pick 24f1402
Backport kubernetes-sigs#8339 to 2.18-release Cherry-pick 24f1402
Backport #8339 to 2.18-release Cherry-pick 24f1402 Co-authored-by: Choi Yongbeom <[email protected]>
* Update prep_download.yml nerdctl insecure registry config * Update prep_download.yml * Update prep_download.yml apply conversations advice * Update prep_download.yml * Update prep_download.yml * Update prep_download.yml * Update prep_download.yml * Update prep_download.yml * Update prep_download.yml * Update main.yml * Update main.yml * Update prep_download.yml * Update prep_download.yml
* Update prep_download.yml nerdctl insecure registry config * Update prep_download.yml * Update prep_download.yml apply conversations advice * Update prep_download.yml * Update prep_download.yml * Update prep_download.yml * Update prep_download.yml * Update prep_download.yml * Update prep_download.yml * Update main.yml * Update main.yml * Update prep_download.yml * Update prep_download.yml
* Update prep_download.yml nerdctl insecure registry config * Update prep_download.yml * Update prep_download.yml apply conversations advice * Update prep_download.yml * Update prep_download.yml * Update prep_download.yml * Update prep_download.yml * Update prep_download.yml * Update prep_download.yml * Update main.yml * Update main.yml * Update prep_download.yml * Update prep_download.yml
nerdctl insecure registry config
nerdctl insecure config doesn't refer to containerd config (/etc/containerd/config.toml)
currently nerdctl can't use insecure registry
to download from insecure registry using nerdctl must be use --insecure-registy option
What type of PR is this?
What this PR does / why we need it:
/kind feature
Which issue(s) this PR fixes:
Fixes #8336
Special notes for your reviewer:
Does this PR introduce a user-facing change?: