Probleme start minikube v1.25.0 dans windows 10 avec Docker Desktop 4.15.0

[nacerkraa]

I run:
minikube start --driver= docker
And I get this error on my cmd:

Output

* minikube v1.25.0 sur Microsoft Windows 10 Pro 10.0.19045 Build 19045 * Utilisation du pilote docker basé sur le profil existant * Démarrage du noeud de plan de contrôle minikube dans le cluster minikube * Extraction de l'image de base... * docker "minikube" container est manquant, il va être recréé. * Création de docker container (CPUs=2, Memory=2200Mo) ... ! StartHost a échoué, mais va réessayer : recreate: creating host: create: creating: prepare kic ssh: unable to execute icacls to set permissions: exit status 1 * Mise à jour du container docker en marche "minikube" ... * Préparation de Kubernetes v1.23.1 sur Docker 20.10.12... - kubelet.housekeeping-interval=5m ! l'initialisation a échoué, va réessayer : wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.23.1:$PATH" kubeadm init --config /var/tmp/minikube/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,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,Mem,SystemVerification,FileContent--proc-sys-net-bridge-bridge-nf-call-iptables": Process exited with status 3

stdout:

stderr:
apiServer.certSANs: Invalid value: "": altname is not a valid IP address, DNS label or a DNS label with subdomain wildcards: a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is 'a-z0-9?(.a-z0-9?)'); a wildcard DNS-1123 subdomain must start with '.', followed by a valid DNS subdomain, which must consist of lower case alphanumeric characters, '-' or '.' and end with an alphanumeric character (e.g. '.example.com', regex used for validation is '*.a-z0-9?(.a-z0-9?)')
To see the stack trace of this error execute with --v=5 or higher

X Erreur lors du démarrage du cluster: wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.23.1:$PATH" kubeadm init --config /var/tmp/minikube/kubeadm.yaml
--ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,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,Mem,SystemVerification,FileContent--proc-sys-net-bridge-bridge-nf-call-iptables": Process exited with status 3
stdout:

stderr:
apiServer.certSANs: Invalid value: "": altname is not a valid IP address, DNS label or a DNS label with subdomain wildcards: a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is 'a-z0-9?(.a-z0-9?)'); a wildcard DNS-1123 subdomain must start with '.', followed by a valid DNS subdomain, which must consist of lower case alphanumeric characters, '-' or '.' and end with an alphanumeric character (e.g. '.example.com', regex used for validation is '*.a-z0-9?(.a-z0-9?)')
To see the stack trace of this error execute with --v=5 or higher

╭────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * Si les conseils ci-dessus ne vous aident pas, veuillez nous en informer : │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Veuillez exécuter minikube logs --file=logs.txt et attachez logs.txt au problème GitHub. │
│ │
╰────────────────────────────────────────────────────────────────────────────────────────────────────╯

X Fermeture en raison de K8S_INVALID_CERT_HOSTNAME : wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.23.1:$PATH" kubeadm init --config /var/tmp/minikube/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,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,Mem,SystemVerification,FileContent--proc-sys-net-bridge-bridge-nf-call-iptables": Process exited with status 3
stdout:

stderr:
apiServer.certSANs: Invalid value: "": altname is not a valid IP address, DNS label or a DNS label with subdomain wildcards: a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is 'a-z0-9?(.a-z0-9?)'); a wildcard DNS-1123 subdomain must start with '.', followed by a valid DNS subdomain, which must consist of lower case alphanumeric characters, '-' or '.' and end with an alphanumeric character (e.g. '.example.com', regex used for validation is '*.a-z0-9?(.a-z0-9?)')
To see the stack trace of this error execute with --v=5 or higher

• Suggestion : Le nom d'hôte du certificat fourni semble être invalide (peut être un bogue minikube, essayez 'minikube delete')
• Problème connexe: minikube unable to recover from empty IP/name: apiServer.certSANs: Invalid value: "":  #9175

╭────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * Si les conseils ci-dessus ne vous aident pas, veuillez nous en informer : │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Veuillez exécuter minikube logs --file=logs.txt et attachez logs.txt au problème GitHub. │
│ │
╰────────────────────────────────────────────────────────────────────────────────────────────────────╯

C:\Users\Nacer
λ /remove-lifecycle stale
'/remove-lifecycle' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.

C:\Users\Nacer
λ minikube logs --file=log.txt
E1228 18:41:08.450253 11144 logs.go:192] command /bin/bash -c "sudo /var/lib/minikube/binaries/v1.23.1/kubectl describe nodes --kubeconfig=/var/lib/minikube/kubeconfig" failed with error: /bin/bash -c "sudo /var/lib/minikube/binaries/v1.23.1/kubectl describe nodes --kubeconfig=/var/lib/minikube/kubeconfig": Process exited with status 1
stdout:

stderr:
E1228 17:41:08.426405 1476 cert_rotation.go:168] key failed with : x509: cannot parse IP address of length 0
E1228 17:41:08.431991 1476 cert_rotation.go:168] key failed with : x509: cannot parse IP address of length 0
The connection to the server localhost:8443 was refused - did you specify the right host or port?
output: "\n** stderr ** \nE1228 17:41:08.426405 1476 cert_rotation.go:168] key failed with : x509: cannot parse IP address of length 0\nE1228 17:41:08.431991 1476 cert_rotation.go:168] key failed with : x509: cannot parse IP address of length 0\nThe connection to the server localhost:8443 was refused - did you specify the right host or port?\n\n** /stderr **"

! unable to fetch logs for: describe nodes

[log.txt](https://github.com/kubernetes/minikube/files/10315624/log.txt)

[k8s-triage-robot]

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