You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 9, 2022. It is now read-only.
There is a private registry running http at localhost, crictl pull images there result failing as below:
Normal Scheduled <unknown> default-scheduler Successfully assigned default/vm-0 to iserver
Warning Failed 39m (x2 over 40m) kubelet, iserver Failed to pull image "localhost:5000/vm-runner:dev": rpc error: code = Unknown desc = failed to pull and unpack image "localhost:5000/vm-runner:dev": failed to resolve reference "localhost:5000/vm-runner:dev": failed to do request: Head https://localhost:5000/v2/vm-runner/manifests/dev: http: server gave HTTP response to HTTPS client
iserver [~]$ crictl -v
crictl github.com/rancher/containerd v1.16.1-k3s.1
Is crictl behave differently from docker?, that is forcing to run https on localhost as well?
The text was updated successfully, but these errors were encountered:
Thanks a lot @Random-Liu! The info is really helpful! could be nice to allow fallback into http on localhost. Since int many cases, especially in a development env. people want a quick and work solution.
For most uses, I guess that's ok, but there could be situations where you want to have that range to use a secure connection as well. I don't think that's currently possible (as it will always add that range to the list of insecure registries).
There is a private registry running http at localhost, crictl pull images there result failing as below:
Is crictl behave differently from docker?, that is forcing to run https on localhost as well?
The text was updated successfully, but these errors were encountered: