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.

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

hyperv: cannot use "fe80::215:5dff:fe2b:530f" as the bind address for the API Server #4693

Closed
kshmaniram opened this issue Jul 5, 2019 · 1 comment
Labels
co/hyperv HyperV related issues triage/duplicate Indicates an issue is a duplicate of other open issue.

Comments

@kshmaniram
Copy link

  • Configuring environment for Kubernetes v1.14.3 on Docker 18.09.6
  • Pulling images ...
  • Unable to pull images, which may be OK: running cmd: sudo kubeadm config images pull --config /var/lib/kubeadm.yaml: command failed: sudo kubeadm config images pull --config /var/lib/kubeadm.yaml
    stdout:
    stderr: failed to pull image "k8s.gcr.io/kube-apiserver:v1.14.3": 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
    : Process exited with status 1
  • Launching Kubernetes ...

X Error starting cluster: cmd failed: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--data-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:fe2b:530f" as the bind address for the API Server

: Process exited with status 1

@afbjorklund afbjorklund added the co/hyperv HyperV related issues label Jul 14, 2019
@tstromberg tstromberg changed the title Minikube start failed in HyperV hyperv: cannot use "fe80::215:5dff:fe2b:530f" as the bind address for the API Server Jul 16, 2019
@tstromberg
Copy link
Contributor

This issue appears to be a duplicate of #3963, so I will close this one so that we may centralize the content relating to the issue. If you feel that this issue is not in fact a duplicate, please feel free to re-open it.

Thank you for reporting this!

@tstromberg tstromberg added the triage/duplicate Indicates an issue is a duplicate of other open issue. label Jul 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/hyperv HyperV related issues triage/duplicate Indicates an issue is a duplicate of other open issue.
Projects
None yet
Development

No branches or pull requests

3 participants