Open WoodpeckerBaby opened 3 years ago
/kind support
Interesting, generally if docker is healthy and available, minikube will automatically choose the docker driver if no driver is explicitly passed into minikube start
.
The hyperkit + VPN issue is a well-known one (see https://github.com/kubernetes/minikube/issues/6296) that we're looking at fixing soon.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
this helped me thank you @WoodpeckerBaby
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
Steps to reproduce the issue:
minikube start
Full output of
minikube logs
command:Full output of failed command:
Troubleshooting
I tried to use
brew rm minikube
, restarted the computer and installed it again, but did not help.About networking and proxy
I have reviewed the proxy documentation mentioned in the logs. I don't need a proxy to access the internet but I'm using a commercial VPN software Astrill, which has a custom VPN driver.
*.local, 169.254/16, 192.168.0.1/16, 10.96.0.0/12
*.local, 192.168.0.1/16, 10.96.0.0/12
minikube start
again, but the same issue. I tried to turn off the VPN all together, and run theminikube start
command again, but the same issue.Edit
I realized a few previous cases
12363
8765
This hotfix solved my issue.
Originally posted by @kenessajr in https://github.com/kubernetes/minikube/issues/8765#issuecomment-828506809
Command line outputs
$ `minikube delete --all --purge` ๐ฅ Deleting "minikube" in hyperkit ... ๐ Removed all traces of the "minikube" cluster. ๐ฅ Successfully deleted all profiles ๐ Successfully purged minikube directory located at - [/Users/fullusername/.minikube] $ `minikube start` ๐ minikube v1.22.0 on Darwin 11.5.2 โจ Automatically selected the hyperkit driver. Other choices: parallels, vmware, ssh ๐พ Downloading driver docker-machine-driver-hyperkit: > docker-machine-driver-hyper...: 65 B / 65 B [----------] 100.00% ? p/s 0s > docker-machine-driver-hyper...: 10.52 MiB / 10.52 MiB 100.00% 9.55 MiB p ๐ The 'hyperkit' driver requires elevated permissions. The following commands will be executed: $ sudo chown root:wheel /Users/fullusername/.minikube/bin/docker-machine-driver-hyperkit $ sudo chmod u+s /Users/fullusername/.minikube/bin/docker-machine-driver-hyperkit Password: ๐ฟ Downloading VM boot image ... > minikube-v1.22.0.iso.sha256: 65 B / 65 B [-------------] 100.00% ? p/s 0s > minikube-v1.22.0.iso: 242.95 MiB / 242.95 MiB [ 100.00% 14.19 MiB p/s 17s ๐ Starting control plane node minikube in cluster minikube ๐พ Downloading Kubernetes v1.21.2 preload ... > preloaded-images-k8s-v11-v1...: 502.14 MiB / 502.14 MiB 100.00% 11.79 Mi ๐ฅ Creating hyperkit VM (CPUs=2, Memory=4000MB, Disk=20000MB) ... โ This VM 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.21.2 on Docker 20.10.6 ... โช Generating certificates and keys ... โช Booting up control plane ... โช Configuring RBAC rules ... ๐ 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 $ `kubectl get nodes` NAME STATUS ROLES AGE VERSION minikube Ready control-plane,master 9m28s v1.21.2But there is a new issue
Everything looks okay until I tried to create a deployment
I tried
kubectl describe pod nginx-depl-5c8bf76b5b-nhfsc
Command line outputs from describe
Name: nginx-depl-5c8bf76b5b-nhfsc Namespace: default Priority: 0 Node: minikube/192.168.38.4 Start Time: Wed, 01 Sep 2021 22:11:33 +0800 Labels: app=nginx-depl pod-template-hash=5c8bf76b5b Annotations:This problem is likely due to hypervisor issues the way minikube is generated. I fixed this issue by using
minikube start --driver=docker
, you can also set all future ones to use docker hypervisor withminikube config set driver docker
. See, doc for details.