|
|
| (16 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| | {{lowercase}} __NOTOC__ | | {{lowercase}} __NOTOC__ |
| | | | |
| − | [[minikube]] start && [[minikube status]] && [[kubectl get pods -A]] | + | [[minikube]] start && [[minikube status]] && [[Minikube: kubectl get pods -A|kubectl get pods -A]] |
| | + | [[minikube addons enable ingress]] [[csi-hostpath-driver]] |
| | | | |
| | + | [[minikube addons enable]] |
| | | | |
| − | == Mikikube start examples == | + | [[minikube delete]] && [[minikube start]] |
| | + | |
| | + | == [[Mikikube start examples]] == |
| | * <code>[[minikube]] start</code> | | * <code>[[minikube]] start</code> |
| | * <code>[[minikube start --help]]</code> | | * <code>[[minikube start --help]]</code> |
| Line 17: |
Line 21: |
| | * <code>[[minikube start --nodes]] 2 -p my-multinode-demo</code> | | * <code>[[minikube start --nodes]] 2 -p my-multinode-demo</code> |
| | * <code>[[minikube start --listen-address]]=0.0.0.0</code> | | * <code>[[minikube start --listen-address]]=0.0.0.0</code> |
| | + | * [[minikube start -p]] argocd --cpus=4 --disk-size=40gb --memory=8gb |
| | | | |
| − | == [[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
| |
| − | <pre>
| |
| − | <nowiki>
| |
| − |
| |
| − | 😄 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.
| |
| − |
| |
| − | </nowiki>
| |
| − | </pre>
| |
| − |
| |
| − | 😄 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 ===
| |
| − | <pre>
| |
| − | 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
| |
| − | </pre>
| |
| − |
| |
| − |
| |
| − |
| |
| − | 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 v[[1.18.1]] on macOS ===
| |
| − | <pre>
| |
| − | 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
| |
| − | </pre>
| |
| − |
| |
| − | == Version v[[1.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 {{.Server.Os}}-{{.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]] ==
| |
| − | <pre>
| |
| − | 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/
| |
| − | </pre>
| |
| − |
| |
| − | === Version 1.12.3 on macOS ===
| |
| − | <pre>
| |
| − | 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
| |
| − | </pre>
| |
| − |
| |
| − | === 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
| |
| | | | |
| | + | == [[Mikikube start execution examples]] == |
| | == With errors == | | == With errors == |
| | <pre> | | <pre> |
| Line 422: |
Line 38: |
| | | | |
| | == Related terms == | | == Related terms == |
| − | * <code>[[minikube status]]</code>
| |
| − | * <code>[[minikube stop]]</code>
| |
| − | * <code>[[minikube delete]]</code>
| |
| − | * <code>[[minikube config]]</code>
| |
| | * <code>[[snap install docker]]</code> | | * <code>[[snap install docker]]</code> |
| − | * <code>[[docker start]]</code> | + | * <code>[[docker start]], [[docker stop]]</code> |
| − | * <code>[[docker stop]]</code>
| |
| | * [[VirtualBox]] | | * [[VirtualBox]] |
| | * <code>[[kubectl cluster-info]]</code> | | * <code>[[kubectl cluster-info]]</code> |
| Line 437: |
Line 48: |
| | * <code>[[minikube profile list]]</code> | | * <code>[[minikube profile list]]</code> |
| | * <code>[[minikube addons enable metrics-server]]</code> | | * <code>[[minikube addons enable metrics-server]]</code> |
| − | * <code>[[brew uninstall minikube]]</code> | + | * <code>[[kind create cluster]]</code> |
| | + | * [[Katacoda]] |
| | | | |
| | == See also == | | == See also == |
| | * {{minikube start}} | | * {{minikube start}} |
| − | * {{minikube}}
| |
| | | | |
| | [[Category:Minikube]] | | [[Category:Minikube]] |
