minikube start
Mikikube start examples
minikube start
minikube start --help
minikube start --vm=true
minikube start --driver=kvm2
minikube start --driver=docker
minikube start --driver=podman
minikube start --memory 4096
minikube start --cpus 3 --memory 3072
minikube start --container-runtime containerd
minikube start --feature-gates
minikube start --nodes 2 -p my-multinode-demo
minikube start --listen-address=0.0.0.0
macOS
Minikube 1.32.0
๐ minikube v1.32.0 on Darwin 14.2.1 (arm64) ๐ Kubernetes 1.28.3 is now available. If you would like to upgrade, specify: --kubernetes-version=v1.28.3 โจ Using the docker driver based on existing profile ๐ Starting control plane node minikube in cluster minikube ๐ Pulling base image ... ๐คท docker "minikube" container is missing, will recreate. ๐ฅ Creating docker container (CPUs=2, Memory=4000MB) ... โ Image was not built for the current minikube version. To resolve this you can delete and recreate your minikube cluster using the latest images. Expected minikube version: v1.31.0 -> Actual minikube version: v1.32.0 ๐ณ Preparing Kubernetes v1.27.4 on Docker 24.0.4 ... โช Generating certificates and keys ... โช Booting up control plane ... โช Configuring RBAC rules ... ๐ Configuring bridge CNI (Container Networking Interface) ... ๐ก After the addon is enabled, please run "minikube tunnel" and your ingress resources would be available at "127.0.0.1" โช Using image gcr.io/k8s-minikube/storage-provisioner:v5 โช Using image registry.k8s.io/metrics-server/metrics-server:v0.6.4 โช Using image registry.k8s.io/ingress-nginx/kube-webhook- certgen:v20231011-8b53cabe0 โช Using image docker.io/kubernetesui/dashboard:v2.7.0 โช Using image registry.k8s.io/sig-storage/csi-attacher:v4.0.0 โช Using image registry.k8s.io/sig-storage/snapshot- controller:v6.1.0
๐ Verifying Kubernetes components...
โช Using image docker.io/kubernetesui/metrics-scraper:v1.0.8 โช Using image registry.k8s.io/ingress-nginx/kube-webhook-certgen:v20231011-8b53cabe0 โช Using image registry.k8s.io/sig-storage/csi-external-health- monitor-controller:v0.7.0 โช Using image registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.6.0 โช Using image registry.k8s.io/sig-storage/hostpathplugin:v1.9.0 โช Using image registry.k8s.io/ingress-nginx/controller:v1.9.4 โช Using image registry.k8s.io/sig-storage/livenessprobe:v2.8.0 โช Using image registry.k8s.io/sig-storage/csi-resizer:v1.6.0 โช Using image registry.k8s.io/sig-storage/csi-snapshotter:v6.1.0 โช Using image registry.k8s.io/sig-storage/csi-provisioner:v3.3.0 ๐ Verifying ingress addon... ๐ก Some dashboard features require the metrics-server addon. To enable all features please run:
minikube addons enable metrics-server
๐ Verifying csi-hostpath-driver addon...
Minikube 1.31.2
๐ minikube v1.31.2 on Darwin 13.5.2 (arm64) โจ Automatically selected the docker driver ๐ Using Docker Desktop driver with root privileges ๐ Starting control plane node minikube in cluster minikube ๐ Pulling base image ... ๐พ Downloading Kubernetes v1.27.4 preload ... > preloaded-images-k8s-v18-v1...: 327.74 MiB / 327.74 MiB 100.00% 492.53 ยงยง > gcr.io/k8s-minikube/kicbase...: 404.50 MiB / 404.50 MiB 100.00% 490.36 ๐ฅ Creating docker container (CPUs=2, Memory=4000MB) ... ๐ณ Preparing Kubernetes v1.27.4 on Docker 24.0.4 ... โช Generating certificates and keys ... โช Booting up control plane ... โช Configuring RBAC rules ... ๐ Configuring bridge CNI (Container Networking Interface) ... โช Using image gcr.io/k8s-minikube/storage-provisioner:v5 ๐ Verifying Kubernetes components... ๐ Enabled addons: default-storageclass, storage-provisioner ๐ Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
Minikube 1.27.1
minikube start ๐ minikube v1.27.1 on Ubuntu 22.04 (arm64) โจ Automatically selected the docker driver. Other choices: ssh, none โ Exiting due to RSRC_INSUFFICIENT_CORES: Requested cpu count 2 is greater than the available cpus of 1
๐ minikube v1.27.1 on Ubuntu 22.04 (arm64) ๐ Unable to pick a default driver. Here is what was considered, in preference order: โช docker: Not healthy: "docker version --format {{.Server.Os}}-{{.Server.Version}}" exit status 1: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/version": dial unix /var/run/docker.sock: connect: permission denied โช docker: Suggestion: Add your user to the 'docker' group: 'sudo usermod -aG docker $USER && newgrp docker' <https://docs.docker.com/engine/install/linux-postinstall/> ๐ก Alternatively you could install one of these drivers: โช kvm2: Not installed: exec: "virsh": executable file not found in $PATH โช vmware: Not installed: exec: "docker-machine-driver-vmware": executable file not found in $PATH โช podman: Not installed: exec: "podman": executable file not found in $PATH โช virtualbox: Not installed: unable to find VBoxManage in $PATH โช qemu2: Not installed: exec: "qemu-system-aarch64": executable file not found in $PATH โ Exiting due to DRV_NOT_HEALTHY: Found driver(s) but none were healthy. See above for suggestions how to fix installed drivers.
๐ minikube v1.27.1 on Ubuntu 22.04 (arm64) โช MINIKUBE_ROOTLESS=true โจ Automatically selected the podman driver โ Exiting due to RSRC_INSUFFICIENT_CONTAINER_MEMORY: podman only has 961MiB available, less than the required 1800MiB for Kubernetes
๐ minikube v1.27.1 on Ubuntu 22.04 (arm64) โช MINIKUBE_ROOTLESS=true โจ Automatically selected the podman driver ๐ Using rootless Podman driver โ Exiting due to MK_USAGE: --container-runtime must be set to "containerd" or "cri-o" for rootless
.../... ๐ฟ Failed to start podman container. Running "minikube delete" may fix it: creating host: create: creating: setting up container node: creating volume for minikube container: podman volume create minikube --label name.minikube.sigs.k8s.io=minikube --label created_by.minikube.sigs.k8s.io=true: exit status 125 stdout: stderr: Error: volume with name minikube already exists: volume already exists โ Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: creating: setting up container node: creating volume for minikube container: podman volume create minikube --label name.minikube.sigs.k8s.io=minikube -- label created_by.minikube.sigs.k8s.io=true: exit status 125 stdout: stderr: Error: volume with name minikube already exists: volume already exists
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ โ
โ ๐ฟ If the above advice does not help, please let us know: โ
โ ๐ https://github.com/kubernetes/minikube/issues/new/choose โ
โ โ
โ Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue. โ
โ โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
Minikube 1.27.0
๐ minikube v1.27.0 on Darwin 12.6 (arm64) โ Kubernetes 1.25.0 has a known issue with resolv.conf. minikube is using a workaround that should work for most use cases. โ For more information, see: https://github.com/kubernetes/kubernetes/issues/112135 โจ Using the docker driver based on existing profile ๐ Starting control plane node minikube in cluster minikube ๐ Pulling base image ... ๐ Restarting existing docker container for "minikube" ... ๐ณ Preparing Kubernetes v1.25.0 on Docker 20.10.17 ... ๐ Verifying Kubernetes components... โช Using image gcr.io/k8s-minikube/storage-provisioner:v5 ๐ Enabled addons: default-storageclass, storage-provisioner ๐ Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
Minikube 1.25.2
.../... โ Problems detected in kubelet: May 19 15:25:56 minikube kubelet[179323]: E0519 15:25:56.304268 179323 kubelet.go:1431] "Failed to start ContainerManager" err=" [open /proc/sys/vm/overcommit_memory: permission denied, open /proc/sys/kernel/panic: permission denied, open /proc/sys/kernel/panic_on_oops: permission denied]"
Minikube 1.25.2
minikube start ๐ minikube v1.25.2 on Darwin 12.0.1 (arm64) โจ Using the docker driver based on existing profile ๐ฃ Exiting due to PROVIDER_DOCKER_VERSION_EXIT_1: "docker version --format -" exit status 1: Error response from daemon: Bad response from Docker engine ๐ Documentation: https://minikube.sigs.k8s.io/docs/drivers/docker/
minikube start ๐ minikube v1.25.2 on Darwin 12.5.1 (arm64) โจ Using the docker driver based on existing profile ๐ฃ Exiting due to PROVIDER_DOCKER_VERSION_EXIT_1: "docker version --format -" exit status 1: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/version": dial unix /var/run/docker.sock: connect: permission denied ๐ Documentation: https://minikube.sigs.k8s.io/docs/drivers/docker/
Minikube 1.25.2
๐ minikube v1.25.2 on Darwin 12.5.1 (arm64) โจ Using the podman (experimental) driver based on existing profile ๐ฃ Exiting due to PROVIDER_PODMAN_NOT_RUNNING: "podman version --format " exit status 125: Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman. failed to create sshClient: connection to bastion host (ssh://core@localhost:51276/run/user/501/podman/podman.sock) failed: dial tcp [::1]:51276: connect: connection refused ๐ Documentation: https://minikube.sigs.k8s.io/docs/drivers/podman/
Minikube v1.25.1
minikube start ๐ minikube v1.25.1 on Darwin 12.0.1 (arm64) โจ Automatically selected the docker driver ๐ Starting control plane node minikube in cluster minikube ๐ Pulling base image ... ๐พ Downloading Kubernetes v1.23.1 preload ... > preloaded-images-k8s-v16-v1...: 417.88 MiB / 417.88 MiB 100.00% 1.61 MiB > gcr.io/k8s-minikube/kicbase: 343.02 MiB / 343.02 MiB 100.00% 1.18 MiB p/ ๐ฅ Creating docker container (CPUs=2, Memory=1988MB) ... ๐ณ Preparing Kubernetes v1.23.1 on Docker 20.10.12 ... โช kubelet.housekeeping-interval=5m โช Generating certificates and keys ... โช Booting up control plane ... โช Configuring RBAC rules ... ๐ Verifying Kubernetes components... โช Using image gcr.io/k8s-minikube/storage-provisioner:v5 ๐ Enabled addons: default-storageclass, storage-provisioner ๐ Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
Minikube v1.25.1 with errors
minikube start ๐ minikube v1.25.1 on Darwin 12.0.1 (arm64) ๐ Unable to pick a default driver. Here is what was considered, in preference order: ๐ก Alternatively you could install one of these drivers: โช docker: Not installed: exec: "docker": executable file not found in $PATH โช hyperkit: Not installed: exec: "hyperkit": executable file not found in $PATH โช parallels: Not installed: exec: "prlctl": executable file not found in $PATH โช vmware: Not installed: exec: "docker-machine-driver-vmware": executable file not found in $PATH โช virtualbox: Not installed: unable to find VBoxManage in $PATH โช podman: Not installed: exec: "podman": executable file not found in $PATH โ Exiting due to DRV_NOT_DETECTED: No possible driver was detected. Try specifying --driver, or see https://minikube.sigs.k8s.io/docs/start/
Minikube v1.22.0
minikube start ๐ minikube v1.22.0 on Darwin 11.3 โจ Using the virtualbox driver based on existing profile ๐ Starting control plane node minikube in cluster minikube ๐ Restarting existing virtualbox VM for "minikube" ... โ This VM is having trouble accessing https://k8s.gcr.io ๐ก To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/ ๐ณ Preparing Kubernetes v1.21.2 on Docker 20.10.6 ... โช Generating certificates and keys ... โช Booting up control plane ... โช Configuring RBAC rules ... ๐ Verifying Kubernetes components... โช Using image gcr.io/k8s-minikube/storage-provisioner:v5 ๐ Enabled addons: storage-provisioner, default-storageclass ๐ Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
minikube start ๐ minikube v1.22.0 on Darwin 11.3 โจ Automatically selected the virtualbox driver ๐ฟ Downloading VM boot image ... > minikube-v1.22.0.iso.sha256: 65 B / 65 B [-------------] 100.00% ? p/s 0s > minikube-v1.22.0.iso: 242.95 MiB / 242.95 MiB 100.00% 1.56 MiB p/s 2m36s ๐ Starting control plane node minikube in cluster minikube ๐พ Downloading Kubernetes v1.21.2 preload ... > preloaded-images-k8s-v11-v1...: 502.14 MiB / 502.14 MiB 100.00% 1.29 MiB ๐ฅ Creating virtualbox VM (CPUs=2, Memory=2200MB, Disk=20000MB) ... ๐ฅ Deleting "minikube" in virtualbox ... ๐คฆ StartHost failed, but will try again: creating host: create: creating: Error setting up host only network on machine start: The host- only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue ๐ฅ Creating virtualbox VM (CPUs=2, Memory=2200MB, Disk=20000MB) ... ๐ฟ Failed to start virtualbox VM. Running "minikube delete" may fix it: creating host: create: creating: Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue โ Exiting due to IF_VBOX_NOT_VISIBLE: Failed to start host: creating host: create: creating: Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue ๐ก Suggestion: Reboot to complete VirtualBox installation, verify that VirtualBox is not blocked by your system, and/or use another hypervisor ๐ Documentation: https://stackoverflow.com/questions/52277019/how-to-fix-vm-issue-with-minikube-start ๐ฟ Related issues: โช https://github.com/kubernetes/minikube/issues/3614 โช https://github.com/kubernetes/minikube/issues/4222 โช https://github.com/kubernetes/minikube/issues/5817
Minikube v1.18.1 on macOS
minikube start ๐ minikube v1.18.1 on Darwin 10.14.6 ๐ Kubernetes 1.20.2 is now available. If you would like to upgrade, specify: --kubernetes-version=v1.20.2 โจ Using the docker driver based on existing profile ๐ Starting control plane node minikube in cluster minikube ๐ Restarting existing docker container for "minikube" ... ๐ณ Preparing Kubernetes v1.18.3 on Docker 19.03.8 ... ๐ Verifying Kubernetes components... โช Using image kubernetesui/dashboard:v2.1.0 โช Using image kubernetesui/metrics-scraper:v1.0.4 โช Using image bitnami/kubectl:1.17 โช Using image gcr.io/k8s-minikube/storage-provisioner:v4 โช Using image heketi/heketi:10 โช Using image gluster/glusterfile-provisioner:latest โช Using image quay.io/nixpanic/glusterfs-server:pr_fake-disk ๐ Enabled addons: storage-provisioner-gluster, default-storageclass, dashboard ๐ Done! kubectl is now configured to use "minikube" cluster and "" namespace by default
Version v1.24.0 on WSL
๐ minikube v1.24.0 on Ubuntu 20.04 ๐ Unable to pick a default driver. Here is what was considered, in preference order: โช docker: Not healthy: "docker version --format Template:.Server.Os-Template:.Server.Version" exit status 1: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? โช docker: Suggestion: Start the Docker service <https://minikube.sigs.k8s.io/docs/drivers/docker/> โช kvm2: Not installed: exec: "virsh": executable file not found in $PATH โช vmware: Not installed: exec: "docker-machine-driver-vmware": executable file not found in $PATH โช podman: Not installed: exec: "podman": executable file not found in $PATH โช virtualbox: Not installed: unable to find VBoxManage in $PATH โ Exiting due to DRV_DOCKER_NOT_RUNNING: Found docker, but the docker service isn't running. Try restarting the docker
Version 1.18.1 on Ubuntu 20.10
minikube start ๐ minikube v1.18.1 on Ubuntu 20.10 โจ Automatically selected the docker driver. Other choices: none, ssh ๐ The "docker" driver should not be used with root privileges. ๐ก If you are running minikube within a VM, consider using --driver=none: ๐ https://minikube.sigs.k8s.io/docs/reference/drivers/none/ โ Exiting due to DRV_AS_ROOT: The "docker" driver should not be used with root privileges.
Version 1.18.1 on Ubuntu 20.04
minikube start ๐ minikube v1.18.1 on Ubuntu 20.04 ๐ Unable to pick a default driver. Here is what was considered, in preference order: โช vmware: Not installed: exec: "docker-machine-driver-vmware": executable file not found in $PATH โช docker: Not installed: exec: "docker": executable file not found in $PATH โช kvm2: Not healthy: /usr/bin/virsh domcapabilities --virttype kvm failed: error: failed to get emulator capabilities error: invalid argument: KVM is not supported by '/usr/bin/qemu-system-x86_64' on this host โช none: Not installed: exec: "docker": executable file not found in $PATH โช podman: Not installed: exec: "podman": executable file not found in $PATH โช virtualbox: Not installed: unable to find VBoxManage in $PATH โ Exiting due to DRV_NOT_DETECTED: No possible driver was detected. Try specifying --driver, or see https://minikube.sigs.k8s.io/docs/start/
Version 1.12.3 on macOS
minikube start ๐ minikube v1.12.3 on Darwin 10.14.6 โจ Automatically selected the docker driver โ Increase Docker for Desktop memory to at least 2.5GB or more: Docker for Desktop > Settings > Resources > Memory โ Requested memory allocation (1990MB) is less than the recommended minimum 2000MB. Kubernetes may crash unexpectedly. โ Your system has 16384MB memory but Docker has only 1990MB. For a better performance increase to at least 3GB. Docker for Desktop > Settings > Resources > Memory ๐ Starting control plane node minikube in cluster minikube ๐ Pulling base image ... ๐พ Downloading Kubernetes v1.18.3 preload ... > preloaded-images-k8s-v5-v1.18.3-docker-overlay2-amd64.tar.lz4: 510.91 MiB ๐ฅ Creating docker container (CPUs=2, Memory=1990MB) ... ๐ณ Preparing Kubernetes v1.18.3 on Docker 19.03.8 ... ๐ Verifying Kubernetes components... ๐ Enabled addons: default-storageclass, storage-provisioner ๐ Done! kubectl is now configured to use "minikube" โ /usr/local/bin/kubectl is version 1.16.6-beta.0, which may be incompatible with Kubernetes 1.18.3. ๐ก You can also use 'minikube kubectl -- get pods' to invoke a matching version
Version v1.9.2 on macOS
minikube start ๐ minikube v1.9.2 on Darwin 10.14.6 โจ Automatically selected the hyperkit driver ๐พ Downloading driver docker-machine-driver-hyperkit: > docker-machine-driver-hyperkit.sha256: 65 B / 65 B [---] 100.00% ? p/s 0s > docker-machine-driver-hyperkit: 10.90 MiB / 10.90 MiB 100.00% 4.61 MiB p ๐ The 'hyperkit' driver requires elevated permissions. The following commands will be executed: $ sudo chown root:wheel /Users/USERNAME/.minikube/bin/docker-machine-driver-hyperkit $ sudo chmod u+s /Users/USERNAME/.minikube/bin/docker-machine-driver-hyperkit ๐ฟ Downloading VM boot image ... > minikube-v1.9.0.iso.sha256: 65 B / 65 B [--------------] 100.00% ? p/s 0s > minikube-v1.9.0.iso: 174.93 MiB / 174.93 MiB [] 100.00% 13.98 MiB p/s 12s ๐ Starting control plane node m01 in cluster minikube ๐พ Downloading Kubernetes v1.18.0 preload ... > preloaded-images-k8s-v2-v1.18.0-docker-overlay2-amd64.tar.lz4: 542.91 MiB ๐ฅ Creating hyperkit VM (CPUs=2, Memory=4000MB, Disk=20000MB) ... ๐ณ Preparing Kubernetes v1.18.0 on Docker 19.03.8 ... ๐ Enabling addons: default-storageclass, storage-provisioner ๐ Done! kubectl is now configured to use "minikube" โ /usr/local/bin/kubectl is v1.15.5, which may be incompatible with Kubernetes v1.18.0. ๐ก You can also use 'minikube kubectl -- get pods' to invoke a matching version
With errors
minikube start Starting local Kubernetes cluster... E0820 12:06:07.966435 2393 start.go:83] Error starting host: Error creating new host: dial tcp: missing address. Retrying. E0820 12:06:07.979545 2393 start.go:83] Error starting host: Error creating new host: dial tcp: missing address. Retrying. E0820 12:06:07.994242 2393 start.go:83] Error starting host: Error creating new host: dial tcp: missing address. Retrying. E0820 12:06:07.994465 2393 start.go:89] Error starting host: Error creating new host: dial tcp: missing address Error creating new host: dial tcp: missing address Error creating new host: dial tcp: missing address
Related terms
minikube status
minikube stop
minikube delete
minikube config
snap install docker
docker start
docker stop
- VirtualBox
kubectl cluster-info
kubectl config view
docker, hyperkit, parallels, vmware, virtualbox, podman
- Icons
kubectl get pods -A
minikube profile list
minikube addons enable metrics-server
brew uninstall minikube
See also
minikube start [ --listen-address | --nodes ]
- minikube: [
status
|start
|stop
|version
|addons
|addons list
|addons enable
|dashboard
|logs
|tunnel
|ssh
|config
|image | delete
],config set
minikube start --vm=true
, kicbase,~/.minikube/, minikube --help
, Minikube changelog
Advertising: