Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Minikube not working in Windows 8

I'm new to Kubernetes. With the help of Kubernetes documentation , I installed minikube(v0.24.1) and kubectl in my Windows machine. VirtualBox(Version 5.1.18) is also installed in my machine.

Before starting the minikube, i have executed set HTTP_PROXY=xx.xx.xx:8080 and set NO_PROXY=localhost,127.0.0.0/8,192.0.0.0/8 in Windows command prompt

Started minikube by passing Proxy Details :

C:\minikube>minikube start --memory 4096  --vm-driver=virtualbox --docker-env http_proxy=xx.xx.xx:8080  --docker-env https_proxy=xx.xx.xx:8080 --docker-env no_proxy=localhost,127.0.0.0/8,192.0.0.0/8 --cache-images=false
Starting local Kubernetes v1.9.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
Kubectl is now configured to use the cluster.
Loading cached images from config file.

Error from Kubectl :

C:\minikube>kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2017-12-15T21:07:38Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"windows/amd64"}
Unable to connect to the server: dial tcp 192.168.99.100:8443: connectex: An attempt was made to access a socket in a way forbidden by its access permissions.

Minikube Logs:

Feb 01 08:48:35 minikube localkube[2941]: E0201 08:48:35.223594    2941 proxier.go:1701] Failed to delete stale service IP 10.96.0.10 connections, error: error deleting connection tracking
 file not found in $PATH
Feb 01 08:48:38 minikube localkube[2941]: I0201 08:48:38.738404    2941 node_controller.go:857] Controller detected that some Nodes are Ready. Exiting master disruption mode.
Feb 01 08:48:45 minikube localkube[2941]: W0201 08:48:45.765543    2941 conversion.go:110] Could not get instant cpu stats: different number of cpus
Feb 01 08:48:55 minikube localkube[2941]: W0201 08:48:55.776172    2941 conversion.go:110] Could not get instant cpu stats: different number of cpus
Feb 01 08:49:24 minikube localkube[2941]: E0201 08:49:24.338731    2941 healthcheck.go:317] Failed to start node healthz on 0: listen tcp: address 0: missing port in address
Feb 01 08:50:24 minikube localkube[2941]: E0201 08:50:24.341890    2941 healthcheck.go:317] Failed to start node healthz on 0: listen tcp: address 0: missing port in address
Feb 01 08:51:24 minikube localkube[2941]: E0201 08:51:24.342845    2941 healthcheck.go:317] Failed to start node healthz on 0: listen tcp: address 0: missing port in address
Feb 01 08:52:24 minikube localkube[2941]: E0201 08:52:24.344497    2941 healthcheck.go:317] Failed to start node healthz on 0: listen tcp: address 0: missing port in address
Feb 01 08:53:24 minikube localkube[2941]: E0201 08:53:24.349095    2941 healthcheck.go:317] Failed to start node healthz on 0: listen tcp: address 0: missing port in address
Feb 01 08:54:24 minikube localkube[2941]: E0201 08:54:24.351143    2941 healthcheck.go:317] Failed to start node healthz on 0: listen tcp: address 0: missing port in address

How to fix this issue?

like image 354
user2439278 Avatar asked Jan 24 '18 09:01

user2439278


People also ask

Can we run minikube in Windows?

For installation, Minikube offers multiple options such as a simple executable, using the Windows Package Manager, or the Chocolatey Package Manager. You can use any of the options mentioned above to install Minikube.

Do I need kubectl for minikube?

No, minikube comes with a built-in kubectl installation.

Do we need hypervisor for minikube?

Minikube requires a virtual machine manager or a hypervisor (eg: Virtual Box, VMware, Hyperkit, Hyper-V, KVM, etc) and Kubernetes command-line tool which is known as kubectl to interact with your Kubernetes workloads and services. You can use the below link to install Minikube based on your operating system.


1 Answers

As @ivthillo already was pointing out, the issue may occur because you are behind a proxy. In this link they explain solutions to configure minikube when you are behind a proxy: https://github.com/kubernetes/minikube/issues/530#issuecomment-250801735

Try starting minikube like this:

minikube start --docker-env HTTP_PROXY=http://$YOURPROXY:PORT \ --docker-env HTTPS_PROXY=https://$YOURPROXY:PORT

This should configure docker to use your proxy.

Here they also propose other solutions: https://github.com/kubernetes/minikube/issues/530#issuecomment-347718692

like image 198
Javier Salmeron Avatar answered Oct 29 '22 23:10

Javier Salmeron