We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Containerd has preferred using docker-style certs.d via the CRI config_path values, since the 1.5 release. Ref: https://github.com/containerd/containerd/blob/main/docs/hosts.md#cri
certs.d
config_path
[plugins."io.containerd.grpc.v1.cri".registry] config_path = "/etc/containerd/certs.d"
stargz should support this, instead of requiring inline config under the plugins."io.containerd.snapshotter.v1.stargz".registry.mirrors table key
plugins."io.containerd.snapshotter.v1.stargz".registry.mirrors
Current:
[plugins."io.containerd.snapshotter.v1.stargz".registry.mirrors."docker.io"] endpoint = ["https://registry.example.com/v2"]
Preferred:
[plugins."io.containerd.snapshotter.v1.stargz".registry] config_path = "/etc/containerd/certs.d"
The text was updated successfully, but these errors were encountered:
I guess this has actually been supported since #331, but I wasn't aware of that when I refactored the registry stuff in k3s-io/k3s#8973
Sorry, something went wrong.
No branches or pull requests
Containerd has preferred using docker-style
certs.d
via the CRIconfig_path
values, since the 1.5 release.Ref: https://github.com/containerd/containerd/blob/main/docs/hosts.md#cri
stargz should support this, instead of requiring inline config under the
plugins."io.containerd.snapshotter.v1.stargz".registry.mirrors
table keyCurrent:
Preferred:
The text was updated successfully, but these errors were encountered: