Qemu without dedicated network: "'default-storageclass' returned an error"

Leningrad-Sniper commented 4 months ago

What Happened?

😄 minikube v1.33.1 on Debian bookworm/sid ✨ Automatically selected the qemu2 driver. Other choices: ssh, none 🌐 Automatically selected the builtin network ❗ You are using the QEMU driver without a dedicated network, which doesn't support minikube service & minikube tunnel commands. 💿 Downloading VM boot image ...

minikube-v1.33.1-amd64.iso....: 65 B / 65 B [---------] 100.00% ? p/s 0s minikube-v1.33.1-amd64.iso: 314.16 MiB / 314.16 MiB 100.00% 1.59 MiB p/ 👍 Starting "minikube" primary control-plane node in "minikube" cluster 💾 Downloading Kubernetes v1.30.0 preload ... preloaded-images-k8s-v18-v1...: 342.90 MiB / 342.90 MiB 100.00% 8.19 Mi 🔥 Creating qemu2 VM (CPUs=2, Memory=2200MB, Disk=20000MB) ... 🐳 Preparing Kubernetes v1.30.0 on Docker 26.0.2 ... ▪ 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:33071/apis/storage.k8s.io/v1/storageclasses": dial tcp [::1]:33071: connect: connection refused] E0517 05:28:07.442793 8205 start.go:159] Unable to scale down deployment "coredns" in namespace "kube-system" to 1 replica: non-retryable failure while getting "coredns" deployment scale: Get "https://localhost:33071/apis/apps/v1/namespaces/kube-system/deployments/coredns/scale": dial tcp [::1]:33071: connect: connection refused 🌟 Enabled addons: storage-provisioner

Attach the log file

logs.txt

Operating System

Ubuntu

Driver

Docker

medyagh commented 4 months ago

@Leningrad-Sniper I noticed you are not using the socket_vmnet network I am curious if you delete cluster and recreate but install the socket_vmnet first if that fixes your issue ?

https://minikube.sigs.k8s.io/docs/drivers/qemu/

medyagh commented 4 months ago

/triage needs-information /kind support

observabuddy commented 4 months ago

I have the same issue. Running with --driver qemu --network socket_vmnet allows the cluster to come up, but connections to the local host network (e.g. host.minikube.internal) fail, and the ssh container lacks any debugging tools.

chenfli commented 4 months ago

Hitting the same issue no Mac Book. The --netwrok socket_vmnet doesn't change, can't bootstarp the cluster.

spowelljr commented 3 months ago

We have a fix for this, going to close this as a duplicate of https://github.com/kubernetes/minikube/issues/19173 to centralize discussion, please follow there for updates, thank you!

kubernetes / minikube