Minikube start

From wikieduonline
Jump to navigation Jump to search

Examples

Version 1.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 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

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

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 commands

See also

Retrieved from "https://www.wikieduonline.com/index.php?title=Minikube_start&oldid=58688"

Advertising: