unable to reach registry.k8s.io from minikube

[trepository]

What Happened?

When ever i start a minikube, getting "Failing to connect to https://registry.k8s.io/ from inside the minikube container", because of that i am not able to pull any images to the minikube (getting errorimgpull).

Things I did:
docker prune
minikube delete
minikube start

adding minikube ip to the no_proxy or NO_PROXY

Extra debug :

1. Able to access registry.k8s.io from a hostmachine's browser
2. ssh into minikube
3. ping 8.8.8.8 (which is working without any issue)
4. docker login -u (resulted in error getting to register.xxxxx)
5. apt-get update (since minikube is on ubuntu 22.04) , Error updating packages
6. apt-get error : ( Failed to fetch https://download.docker.com/linux/ubuntu/dists/jammy/InRelease Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. The received OCSP status response is invalid. Could not handshake: Error in the certificate verification. [IP: 18.244.61.11 443]
   W: Failed to fetch https://nvidia.github.io/libnvidia-container/stable/deb/amd64/InRelease Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. The received OCSP status response is invalid. Could not handshake: Error in the certificate verification. [IP: 185.199.111.153 443]
   W: Some index files failed to download. They have been ignored, or old ones used instead.)

Can someone please help me in suggesting a workaround?

Environment:
OS: Windows 11 Enterprise
Network : Corporate (No proxy has been added to the pc)

Attach the log file

reloaded_logs.log

Operating System

Windows

Driver

Docker

[venkatschinthakindi]

I too have the same issue since yesterday , I was able to start last week

[plapornik]

This issue also started for me when I upgraded minikube from 1.29.0 to 1.34.0 on computers with W11 23H2 and W11 24H2.

I tried executing "minikube delete --all" to create a new dev environment but the issue persisted during "minikube start".

The driver was set to "hyperv"

I downgraded to minikube 1.33.1 which doesn't have this warning.

[HovhannesHovakimyan]

Same issue.
Windows 11 Pro 24H2, minikube v1.34.0, Docker Desktop v4.36.0

[hharshas]

https://github.com/kubernetes/minikube/issues/15649 I am facing same issue, please someone tell me the solution if there is.