hyperv: cannot use "fe80::215:5dff:fe01:10d" as the bind address for the API Server #5396
Labels
kind/support
Categorizes issue or PR as a support question.
l/es
Issues in or relating to Spanish
triage/duplicate
Indicates an issue is a duplicate of other open issue.
triage/needs-information
Indicates an issue needs more information in order to work on it.
Comments
|
Creo que este problema es un duplicado del #3963, y se puede solucionar actualizando a minikube v1.4 que utiliza el "Interruptor predeterminado" de Hyper-V. ¿Te importaría probarlo por nosotros? |
tstromberg
changed the title
tstromberg
added
triage/duplicate
|
Marking as duplicate of #3963 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Los comandos necesarios para reproducir la incidencia:
El resultado completo del comando que ha fallado:
El resultado del comando
minikube logs: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:fe01:10d" as the bind address for the API Server
La versión del sistema operativo que utilizaste:
The text was updated successfully, but these errors were encountered: