Qemu without dedicated network: "'default-storageclass' returned an error" #18915
Labels
co/qemu-driver
QEMU related issues
kind/regression
Categorizes issue or PR as related to a regression from a prior release.
triage/duplicate
Indicates an issue is a duplicate of other open issue.
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
The text was updated successfully, but these errors were encountered: