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
Mirrors configured in /etc/rancher/k3s/registries.yaml do not take effect #9626
Comments
I believe this is a duplicate of #9341 Remove the second endpoint, you don't need to specify the default endpoint; it is always tried last - and on this specific release it triggers a bug in the registries configuration. |
@brandond I removed the second default endpoint, but the situation is still the same.
|
I'm not sure that ref: https://github.com/containerd/containerd/blob/main/docs/hosts.md |
However, I also tried the same operation using v1.28.5+k3s1. Using v1.28.5+k3s1, I can display the mirror information through crictl info:
Moreover, I also observed that the Containerd versions of v1.28.7+k3s1 and v1.28.5+k3s1 are both |
Because we switched to using hosts.d (configPath) instead of the deprecated inline mirrors config. |
Environmental Info:
K3s Version: v1.28.7+k3s1
Node(s) CPU architecture, OS, and Version: ubuntu 22.04
Cluster Configuration: 1 server
Describe the bug:
When configuring mirrors in /etc/rancher/k3s/registries.yaml, the mirrors do not take effect after starting K3s.
Steps To Reproduce:
Actual behavior:
The configured mirrors are not applied, and the mirrors field remains null in the output of crictl info.
Additional context / logs:
The text was updated successfully, but these errors were encountered: