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.

Sign up for GitHub

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

Jump to bottom

Minikube machine creation errors on hyper-v 2019 #5473

Closed
gurdeepsira opened this issue Sep 26, 2019 · 5 comments
Closed

Minikube machine creation errors on hyper-v 2019 #5473

gurdeepsira opened this issue Sep 26, 2019 · 5 comments
Labels
co/hyperv HyperV related issues triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@gurdeepsira
Copy link

gurdeepsira commented Sep 26, 2019 •
edited by medyagh
Loading

Hi,

I have minikube 1.4.0 and Windows Server 2019.

I run the command:

minikube start -p "test2" --vm-driver=hyperv   --docker-env NO_PROXY=$NO_PROXY

To start the minikube machine, but get the error below:

* Unable to pull images, which may be OK: running cmd: sudo env PATH=/var/lib/minikube/binaries/v1.16.0:$PATH kubeadm config images pull --config /var/tmp/minikube/kubeadm.yaml: command failed: sudo env PATH=/var/lib/minikube/binaries/v1.16.0:$PATH kubeadm config images pull --config /var/tmp/minikube/kubeadm.yaml
stdout:
stderr: failed to pull image "k8s.gcr.io/kube-apiserver:v1.16.0": output: Error response from daemon: Get https://k8s.gcr.io/v2/: dial tcp: lookup k8s.gcr.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
, error: exit status 1
To see the stack trace of this error execute with --v=5 or higher
: Process exited with status 1
* Launching Kubernetes ...
*
X Error starting cluster: cmd failed: sudo env PATH=/var/lib/minikube/binaries/v1.16.0:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml  --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap
cannot use "fe80::215:5dff:fe97:702" as the bind address for the API Server
To see the stack trace of this error execute with --v=5 or higher

: Process exited with status 1
*

I try to run minikube logs, but gt this error:

 command runner: getting ssh client for bootstrapper: Error creating new ssh host from driver: Error getting ssh host name for driver: Host is not running

I am not behind a proxy and ran this command too:

set NO_PROXY=localhost,127.0.0.1,10.96.0.0/12,192.168.99.1/24,192.168.39.0/24
@medyagh
Copy link
Member

medyagh commented Sep 26, 2019

do you mind sharing output of
minikube ip

@medyagh medyagh added co/hyperv HyperV related issues triage/needs-information Indicates an issue needs more information in order to work on it. labels Sep 26, 2019
@medyagh
Copy link
Member

medyagh commented Sep 26, 2019

and also do you mind retrying your commands with this flag
--alsologtostderr -v=8

@gurdeepsira
Copy link
Author

gurdeepsira commented Sep 26, 2019 via email •
edited by medyagh
Loading

@medyagh
Copy link
Member

medyagh commented Sep 27, 2019

ah I think you are on to something ! the IP you add to NO_PROXY is ip v4...

what if you addf the ip v6 to your NO_PROXY env ?

@tstromberg
Copy link
Contributor

This issue appears to be a duplicate of #3963, do you mind if we move the conversation there?

Ths way we can centralize the content relating to the issue. If you feel that this issue is not in fact a duplicate, please re-open it using /reopen. If you have additional information to share, please add it to the new issue.

Thank you for reporting this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
co/hyperv HyperV related issues triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tstromberg @medyagh @gurdeepsira