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 · 9 comments
Open

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

trepository opened this issue Oct 13, 2024 · 9 comments

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

@plapornik
Copy link

plapornik commented Nov 2, 2024

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

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

@hharshas
Copy link

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

@ptiseo-mcs
Copy link

Getting this issue too. Did clean out all containers, images and volumes from dcoker. No proxy or proxying needed on host.

$ minikube start
* minikube v1.35.0 on Microsoft Windows 11 Home 10.0.26100.2894 Build 26100.2894
* Using the docker driver based on existing profile
* Starting "minikube" primary control-plane node in "minikube" cluster
* Pulling base image v0.0.46 ...
* docker "minikube" container is missing, will recreate.
* Creating docker container (CPUs=2, Memory=24500MB) ...
! Failing to connect to https://registry.k8s.io/ from inside the minikube container
* To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/
* Preparing Kubernetes v1.32.0 on Docker 27.4.1 ...
  - Generating certificates and keys ...
  - Booting up control plane ...
  - Configuring RBAC rules ...
* Configuring bridge CNI (Container Networking Interface) ...
* Verifying Kubernetes components...
  - Using image gcr.io/k8s-minikube/storage-provisioner:v5
* Enabled addons: storage-provisioner, default-storageclass
* Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

Ping from host.

$ ping registry.k8s.io

Pinging registry.k8s.io [2600:1901:0:bbc4::] with 32 bytes of data:
Reply from 2600:1901:0:bbc4::: time=25ms
Reply from 2600:1901:0:bbc4::: time=26ms
Reply from 2600:1901:0:bbc4::: time=25ms
Reply from 2600:1901:0:bbc4::: time=23ms

Ping statistics for 2600:1901:0:bbc4:::
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 26ms, Average = 24ms

Ping from minikube environment

$ minikube ssh
docker@minikube:~$ ping registry.k8s.io
PING registry.k8s.io (34.96.108.209) 56(84) bytes of data.
64 bytes from 34.96.108.209 (34.96.108.209): icmp_seq=1 ttl=63 time=26.1 ms
64 bytes from 34.96.108.209 (34.96.108.209): icmp_seq=2 ttl=63 time=26.2 ms
64 bytes from 34.96.108.209 (34.96.108.209): icmp_seq=3 ttl=63 time=25.3 ms
64 bytes from 34.96.108.209 (34.96.108.209): icmp_seq=4 ttl=63 time=24.7 ms
64 bytes from 34.96.108.209 (34.96.108.209): icmp_seq=5 ttl=63 time=24.5 ms
64 bytes from 34.96.108.209 (34.96.108.209): icmp_seq=6 ttl=63 time=18.8 ms
64 bytes from 34.96.108.209 (34.96.108.209): icmp_seq=7 ttl=63 time=21.5 ms
^C
--- registry.k8s.io ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6400ms
rtt min/avg/max/mdev = 18.760/23.860/26.187/2.543 ms

@imadMansour85
Copy link

Same issue anyone solved it ?

@Mayerus
Copy link

Mayerus commented Feb 11, 2025

The issue persists on v1.35 as well. Once I had downgraded to v1.33.1 the problem disappeared.

@dnkalra
Copy link

dnkalra commented Feb 13, 2025

I had similar issues... Followed below article and resolved my problem on windows maching
https://minikube.sigs.k8s.io/docs/handbook/vpn_and_proxy/

On windows machine you can copy and run below commands

set HTTP_PROXY=http://
set HTTPS_PROXY=https://
set 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
minikube start

@Mayerus
Copy link

Mayerus commented Feb 21, 2025

I had similar issues... Followed below article and resolved my problem on windows maching https://minikube.sigs.k8s.io/docs/handbook/vpn_and_proxy/

On windows machine you can copy and run below commands

set HTTP_PROXY=http:// set HTTPS_PROXY=https:// set 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 minikube start

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.

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

9 participants