minikube start

From wikieduonline
Jump to navigation Jump to search

minikube start && minikube status && kubectl get pods -A
minikube addons enable ingress csi-hostpath-driver
minikube addons enable
minikube delete && minikube start

Mikikube start examples

macOS

๐Ÿ˜„  minikube v1.32.0 on Darwin 14.2.1 (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.28.3 preload ...
    > preloaded-images-k8s-v18-v1...:  341.16 MiB / 341.16 MiB  100.00% 18.27 M
    > gcr.io/k8s-minikube/kicbase...:  410.58 MiB / 410.58 MiB  100.00% 16.28 M
๐Ÿ”ฅ  Creating docker container (CPUs=2, Memory=4000MB) ...
๐Ÿณ  Preparing Kubernetes v1.28.3 on Docker 24.0.7 ...\ E0116 17:31:10.012729   79917 kubeadm.go:717] sudo env 
PATH="/var/lib/minikube/binaries/v1.28.3:$PATH" kubeadm init phase certs all --config /var/tmp/minikube/kubeadm.yaml failed - will try once more: /bin/bash 
-c "sudo env PATH="/var/lib/minikube/binaries/v1.28.3:$PATH" kubeadm init phase certs all --config /var/tmp/minikube/kubeadm.yaml": Process exited with 
status 1
stdout:
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk

stderr:
error execution phase certs/apiserver-kubelet-client: [certs] certificate apiserver-kubelet-client not signed by CA certificate ca: x509: certificate 
signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "minikubeCA")
To see the stack trace of this error execute with --v=5 or higher

๐Ÿคฆ  Unable to restart cluster, will reset it: run: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.28.3:$PATH" kubeadm init phase certs all -- config /var/tmp/minikube/kubeadm.yaml": Process exited with status 1 

stdout:

[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
Solution: minikube delete

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

See also

Advertising: