When starting minikube I get the following error in the startup msgs and thus
the container is not usable for me.
…
Failing to connect to https://registry.k8s.io/ from inside the minikube VM
…
I am not behind a proxy or VPN.
– machine env
- minikube (v1.36.0)
- linux (Fedora 42)
- JDK 17
- NO_PROXY=localhost,127.0.0.1,10.96.0.0/12,192.168.59.0/24,192.168.49.0/24,192.168.39.0/24
I’ve run these trouble shooting cmds
curl -sS -m 2 https://registry.k8s.io/
Temporary Redirect
curl -I https://registry.k8s.io/v2
HTTP/2 200
docker-distribution-api-version: registry/2.0
date: Fri, 23 May 2025 22:18:22 GMT
content-type: text/html
server: Google Frontend
via: 1.1 google
alt-svc: h3=“:443”; ma=2592000,h3-29=“:443”; ma=2592000
curl -LI https://registry.k8s.io/v2/pause/tags/list
HTTP/2 307
content-type: text/html; charset=utf-8
location: https://us-east4-docker.pkg.dev/v2/k8s-artifacts-prod/images/pause/tags/list
x-cloud-trace-context: 02442b735f58c97fc041fd9c122df03a
date: Fri, 23 May 2025 22:20:34 GMT
server: Google Frontend
via: 1.1 google
alt-svc: h3=“:443”; ma=2592000,h3-29=“:443”; ma=2592000
HTTP/2 405
content-length: 1458
content-type: text/html; charset=utf-8
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 0
date: Fri, 23 May 2025 22:20:34 GMT
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
Any suggestions as to how to resolve or further debugging actions?