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

Failing to connect to https://registry.k8s.io/ from both inside the minikube container and host machine #20309

Open
shashikumaarb opened this issue Jan 22, 2025 · 0 comments

Comments

@shashikumaarb
Copy link

What Happened?

I am getting this error though I have installed the certificate (I think I copied the certificate to right path).

Failing to connect to https://registry.k8s.io/ from both inside the minikube container and host machine
version: 1.3.0 .... 1.3.5 its happing for any version of 1.3.*

  • Starting "local-cluster-m02" worker node in "local-cluster" cluster
  • Pulling base image v0.0.46 ...
  • Creating docker container (CPUs=2, Memory=1960MB) ...
  • Found network options:
    • NO_PROXY=192.168.49.2
    • NO_PROXY=192.168.49.2
      ! Failing to connect to https://registry.k8s.io/ from both inside the minikube container and host machine
  • 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 ...
    • env NO_PROXY=192.168.49.2
  • Verifying Kubernetes components...
  • Done! kubectl is now configured to use "local-cluster" cluster and "default" namespace by default

Attach the log file

minikube start --mount --mount-string="C:/PLOPS/Prometheus/mount:/mnt/data" --nodes 2 -p local-cluster --driver=docker
please let me know what and which path should I copy the certs.

Operating System

Windows

Driver

Docker

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

1 participant