-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to reach registry.k8s.io from minikube #19798
Comments
I too have the same issue since yesterday , I was able to start last week |
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. |
Same issue. |
https://github.com/kubernetes/minikube/issues/15649 I am facing same issue, please someone tell me the solution if there is. |
Getting this issue too. Did clean out all containers, images and volumes from dcoker. No proxy or proxying needed on host.
Ping from host.
Ping from minikube environment
|
Same issue anyone solved it ? |
The issue persists on v1.35 as well. Once I had downgraded to v1.33.1 the problem disappeared. |
I had similar issues... Followed below article and resolved my problem on windows maching On windows machine you can copy and run below commands set HTTP_PROXY=http:// |
I added HTTPS_PROXY, HTTPS_PROXY and NO_PROXY as system environment variables just like you did, minikube 1.35 detected their values, yet the error persists. Remember to delete these env variables after performing the rollback to 1.33.1. If you don't, the issue will persist. |
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 :
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
The text was updated successfully, but these errors were encountered: