I’m trying to pull a docker image from a private registry from a k3s node based on rancher/k3s
crictl pull 192.168.2.110:5055/xxxx-experiment-on-kubernetes:621477e@sha256:8ac01a28bfe6556d5e39ca38b4846b01e9bc8b86268bf85dc8cb30af82f17284
FATA[2020-05-10T19:43:00.869192875Z] pulling image failed: rpc error: code = Unknown desc = failed to resolve image "192.168.2.110:5055/xxxx-experiment-on-kubernetes@sha256:8ac01a28bfe6556d5e39ca38b4846b01e9bc8b86268bf85dc8cb30af82f17284": no available registry endpoint: failed to do request: Head https://192.168.2.110:5055/v2/xxxx-experiment-on-kubernetes/manifests/sha256:8ac01a28bfe6556d5e39ca38b4846b01e9bc8b86268bf85dc8cb30af82f17284: http: server gave HTTP response to HTTPS client
I added a config.toml.tmpl with the following content
[plugins.opt]
path = "/var/lib/rancher/k3s/agent/containerd"
[plugins.cri]
stream_server_address = "a7d4611f09e0"
stream_server_port = "10010"
[plugins.cri.cni]
bin_dir = "/bin"
conf_dir = "/var/lib/rancher/k3s/agent/etc/cni/net.d
[plugins.cri.registry.mirrors]
[plugins.cri.registry.mirrors."192.168.2.110:5055"]
endpoint = ["http://192.168.2.110:5055"]
[plugins.cri.registry.mirrors."docker.io"]
endpoint = ["https://registry.docker.io"]"
but this does not change the result.
If I mount the file during the container start in the volumes section as
- ./config.toml.tmpl:/var/lib/rancher/k3s/agent/etc/containerd/config.toml.tmpl
the container is not even starting