Skip to content
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

Open
trepository opened this issue Oct 13, 2024 · 1 comment
Open

unable to reach registry.k8s.io from minikube #19798

trepository opened this issue Oct 13, 2024 · 1 comment

Comments

@trepository
Copy link

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
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants