-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
Update rendering containerd config.toml to support insecure registries #9192
Comments
I took another look to the issue and found that the existing configuration can work with containerd 1.6.4, however there is a bug with rendering
the mirror endpoint should be used:
I am tagging this issue as "bug". UPD: looks like I cannot edit labels for the issue, please consider converting this to a bug on your side or let me know if I need to file another issue as a bug. |
I tried this settings with 1.6.4, it does not work, the regsitry.mirror endpoint is skipped. |
@VincentDu2021, works for me for pre-1.7 containerd. Note that nerdctl does not use config.toml from containerd, as far as i understand. This is my my Kubespray configuration snippet that works with insecure registry:
What is your configuration that does not work? |
kubespray 2.19.0
containerd github.com/containerd/containerd v1.6.4 212e8b6fa2f44b9c21b2798135fc6fb7c53efc16
Currently Kubespray allows specifying insecure registries for containerd with parameter
containerd_insecure_registries
, for example:The rendered /etc/containerd/config.toml contains:
Containerd reports the following error:
Per https://github.com/containerd/containerd/blob/main/docs/cri/registry.md this configuration is deprecated and per https://github.com/containerd/containerd/blob/2b661b890f689716b2928408e386e656d8dd7118/pkg/cri/config/config.go#L212 it will be removed in containerd 1.7. Looks like
insecure_skip_verify
is already ignored in containerd 1.6.4.The updated configuration should look like:
/etc/containerd/config.toml
/etc/containerd/certs.d/docker.io/hosts.toml
The text was updated successfully, but these errors were encountered: