difficulté avec minikube

kubernetes / minikube

Run Kubernetes locally

https://minikube.sigs.k8s.io/

Apache License 2.0

29.56k stars 4.89k forks source link

difficulté avec minikube #19239

Open aishasi opened 4 months ago

aishasi commented 4 months ago

Étapes pour reproduire le problème:

1.C:\Windows\System32>minikube start

minikube v1.33.1 sur Microsoft Windows 11 Home 10.0.22635.3858 Build 22635.3858
Choix automatique du pilote hyperv
Démarrage du nœud "minikube" primary control-plane dans le cluster "minikube"
Création de VM hyperv (CPUs=2, Mémoire=2200MB, Disque=20000MB)... ! StartHost a échoué, mais va réessayer : creating host: create: precreate: unable to get available hyperv switches
Création de VM hyperv (CPUs=2, Mémoire=2200MB, Disque=20000MB)...
Échec du démarrage de hyperv VM. L'exécution de "minikube delete" peut résoudre le problème : creating host: create: precreate: unable to get available hyperv switches

X Fermeture en raison de GUEST_PROVISION : error provisioning guest: Failed to start host: creating host: create: precreate: unable to get available hyperv switches *

Sortie complète de la commande minikube logs:

Sortie complète de la commande échouée:

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 2 weeks ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten