Enabling 'default-storageclass' returned an error: running callbacks: [Error making standard the default storage class: Error listing StorageClasses: Get "https://localhost:35935/apis/storage.k8s.io/v1/storageclasses": dial tcp [::1]:35935: connect: connection refused]

[Walyx75]

$ minikube start
😄 minikube v1.33.1 on Fedora 40
✨ Using the qemu2 driver based on existing profile
👍 Starting "minikube" primary control-plane node in "minikube" cluster
🏃 Updating the running qemu2 "minikube" VM ...
🐳 Preparing Kubernetes v1.30.0 on Docker 26.0.2 ...
🤦 Unable to restart control-plane node(s), will reset cluster:
▪ Generating certificates and keys ...
▪ Booting up control plane ...
▪ Configuring RBAC rules ...
🔗 Configuring bridge CNI (Container Networking Interface) ...
🔎 Verifying Kubernetes components...
▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
❗ Enabling 'default-storageclass' returned an error: running callbacks: [Error making standard the default storage class: Error listing StorageClasses: Get "https://localhost:35935/apis/storage.k8s.io/v1/storageclasses": dial tcp [::1]:35935: connect: connection refused]
🌟 Enabled addons: storage-provisioner

❌ Exiting due to GUEST_START: failed to start node: wait 6m0s for node: wait for healthy API server: apiserver healthz never reported healthy: context deadline exceeded

logs.txt

La versión del sistema operativo que utilizaste:
Fedora40

Hola, es la primera vez que detallo un issue.
Tuve problemas en Windows e instalé Fedora para probar Minikube.
Utilicé este link para instalar Minikube
https://geeksterminal.com/install-kubernetes-using-minikube-linux-centos-fedora/3077/

El archivo de log con el problema esta adjunto.
Muchas gracias,

Walter

[Walyx75]

Resuelto,
ejecuté sudo usermod -aG docker $USER && newgrp docker' y luego lo levante con minikube start --driver=docker
No es que es el qemu2
Saludos!

[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

[Walyx75]

/close

[k8s-ci-robot]

@Walyx75: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.