Closed OkayJosh closed 1 year ago
@josvazg's comment was indispensable. Got me going on the right track. A true legend.
In my case, I was using Debian 12.2 with minikube 1.32.0, Kubernetes 1.28.3, Docker 24.0.7.
If you get this error, it means you botched some kind of network config. In my case, I'm using an AWS instance and don't have it set to pull an IPv4 automatically (I'm assigning an Elastic IPv4 as needed). I had forgotten to assign the Elastic IP, so my dango EC2 instance had no way to reach the IPv4 internet.
If you get this error, think about how you set up your instance/server. Did you change DNS settings (as in the case of @josvazg)? Did you make sure you have IP-level network connectivity? Do your basic Linux connectivity commands: ping, ip addr show, etc.
For people using minikube with hyperkit: check that in your firewall settings, the setting for "block all incoming connections" in the Details dialog is not enabled -> it will also block all traffic coming from the bridge.
i am checking back here after this while, seeing that this issue persists? @medyagh
@medyagh yes i was able to fix the issue as at then
Steps to reproduce the issue:
Full output of failed command:
Full output of
minikube start
command used, if not already included:Deleting "minikube" in docker ... 🔥 Deleting container "minikube" ... 🔥 Removing /home/cloudsigma/.minikube/machines/minikube ... 💀 Removed all traces of the "minikube" cluster. [cloudsigma@Fedora-32 django]$ minikube start --driver=docker --image-repository=auto 😄 minikube v1.15.1 on Fedora 32 ✨ Using the docker driver based on user configuration ✅ Using image repository 👍 Starting control plane node minikube in cluster minikube 🔥 Creating docker container (CPUs=2, Memory=2200MB) ... ❗ This container is having trouble accessing https://k8s.gcr.io 💡 To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/ 🐳 Preparing Kubernetes v1.19.4 on Docker 19.03.13 ... 🔎 Verifying Kubernetes components... 🌟 Enabled addons: storage-provisioner, default-storageclass 🏄 Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
Optional: Full output of
minikube logs
command: