Description
We used to run this configuration in our airgapped environments
[plugins."io.containerd.grpc.v1.cri".registry.mirrors]
[plugins."io.containerd.grpc.v1.cri".registry.mirrors."docker.io"]
endpoint = ["https://harbor.schiff.io/v2/hub.docker.com"]
With the new config_path configuration this doesnt seem possible anymore, both
cat /etc/containerd/certs.d/hub.docker.com/hosts.toml
[host."https://harbor.schiff.io/v2/hub.docker.com"]
capabilities = ["pull", "resolve"]
and
cat /etc/containerd/certs.d/hub.docker.com/hosts.toml
[host."https://harbor.schiff.io/hub.docker.com"]
capabilities = ["pull", "resolve"]
arent workibng properly and no images are pulled. The connection works fione if i directly specify an image in that mirror registry, so the fault case must be the mirror cfg
Steps to reproduce the issue:
- use the new container config feature to configure mirrors in an subpathnin a registry klike harbor, artifactory
Describe the results you received:
Mirrooring doesnt work and no images are pulled
Describe the results you expected:
Mirroring works and images get pulled from the specified registries, as before
What version of containerd are you using:
$ containerd --version
1.5.1
Description
We used to run this configuration in our airgapped environments
With the new config_path configuration this doesnt seem possible anymore, both
and
arent workibng properly and no images are pulled. The connection works fione if i directly specify an image in that mirror registry, so the fault case must be the mirror cfg
Steps to reproduce the issue:
Describe the results you received:
Mirrooring doesnt work and no images are pulled
Describe the results you expected:
Mirroring works and images get pulled from the specified registries, as before
What version of containerd are you using: