2

I tried to run minikube with hyperkit driver on VPN. While installing with minikube start --vm=true This error occurred.

❗ This VM is having trouble accessing https://k8s.gcr.io

Someone said from github community, I should use docker but I can not use docker driver for now, because I should install ingress addon, when I tried with docker, it said this addon doesn't work with docker, so it recommends to use the alternative.

Is there any solution to make hyperkit work on VPN?

Rico
  • 58,485
  • 12
  • 111
  • 141
Jacob
  • 21
  • 1
  • 5

2 Answers2

1

This is a known issue. You can try using --vmdriver=virtualbox or --vmdriver=vmwarefusion. Note that you will either have to install VirtualBox or VMware Fusion (Paid license required)

Rico
  • 58,485
  • 12
  • 111
  • 141
  • Thank you , I tried with virtualbox but there is another issue. `❌ Problems detected in kubelet: Oct 06 22:23:34 minikube kubelet[4062]: E1006 22:23:34.576534 4062 pod_workers.go:191] Error syncing pod ff7d12f9e4f14e202a85a7c5534a3129 ("kube-scheduler-minikube_kube-system(ff7d12f9e4f14e202a85a7c5534a3129)"), skipping: failed to "StartContainer" for "kube-scheduler" with RunContainerError: "failed to start container \"510ed6954ca7360ad9d9525ad37fcaf12bc47bed21e31bc65b7a1bf10038f7d1\": Error response from daemon: cannot join network of a non running container:` – Jacob Oct 07 '20 at 16:58
  • Can you uninstall your VPN to discard that the VPN is the issue? – Rico Oct 07 '20 at 22:08
0

I'm on Mac and I faced the same issue. I solved it by applying the flag --hyperkit-vpnkit-sock=auto to minikube start --vm=true. This will, according to the docs:

Location of the VPNKit socket used for networking. If empty, disables Hyperkit VPNKitSock, if 'auto' uses Docker for Mac VPNKit connection, otherwise uses the specified VSock (hyperkit driver only)

marcus_t
  • 36
  • 1
  • 6