Difference between revisions of "Minikube start --vm=true"

From wikieduonline
Jump to navigation Jump to search
Tags: Mobile web edit, Mobile edit
Line 1: Line 1:
  
<pre>
+
 
minikube start --vm=true
+
 
😄  minikube v1.18.1 on Darwin 10.14.6
+
[[minikube start]] --vm=true
🆕  Kubernetes 1.20.2 is now available. If you would like to upgrade, specify: --kubernetes-version=v1.20.2
+
😄  minikube v1.18.1 on Darwin 10.14.6
✨  Using the docker driver based on existing profile
+
🆕  Kubernetes 1.20.2 is now available. If you would like to upgrade, specify: --kubernetes-version=v1.20.2
👍  Starting control plane node minikube in cluster minikube
+
✨  Using the docker driver based on existing profile
🔄  Restarting existing docker container for "minikube" ...
+
👍  Starting control plane node minikube in cluster minikube
🐳  Preparing Kubernetes v1.18.3 on Docker 19.03.8 ...
+
🔄  Restarting existing docker container for "minikube" ...
🔎  Verifying Kubernetes components...
+
🐳  Preparing Kubernetes v1.18.3 on Docker 19.03.8 ...
    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v4
+
🔎  Verifying Kubernetes components...
    ▪ Using image kubernetesui/dashboard:v2.1.0
+
    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v4
    ▪ Using image kubernetesui/metrics-scraper:v1.0.4
+
    ▪ Using image kubernetesui/dashboard:v2.1.0
    ▪ Using image bitnami/kubectl:1.17
+
    ▪ Using image kubernetesui/metrics-scraper:v1.0.4
❗  Enabling 'storage-provisioner-gluster' returned an error: running callbacks: [Error making glusterfile the default storage class: Error while marking storage class glusterfile as default: Operation cannot be fulfilled on storageclasses.storage.k8s.io "glusterfile": the object has been modified; please apply your changes to the latest version and try again]
+
    ▪ Using image bitnami/kubectl:1.17
🌟  Enabled addons: storage-provisioner, kubevirt, default-storageclass, dashboard
+
❗  Enabling 'storage-provisioner-gluster' returned an error: running callbacks: [Error making glusterfile the default storage class: Error while marking storage class glusterfile as default: Operation cannot  
🏄  Done! kubectl is now configured to use "minikube" cluster and "" namespace by default
+
be fulfilled on storageclasses.storage.k8s.io "glusterfile": the object has been modified; please apply your changes to the latest version and try again]
</pre>
+
🌟  Enabled addons: storage-provisioner, kubevirt, default-storageclass, dashboard
 +
🏄  Done! kubectl is now configured to use "minikube" cluster and "" namespace by default
 +
 
  
 
== v1.15.1 ==
 
== v1.15.1 ==

Revision as of 08:05, 19 April 2021


minikube start --vm=true
😄  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 gcr.io/k8s-minikube/storage-provisioner:v4
    ▪ Using image kubernetesui/dashboard:v2.1.0
    ▪ Using image kubernetesui/metrics-scraper:v1.0.4
    ▪ Using image bitnami/kubectl:1.17
❗  Enabling 'storage-provisioner-gluster' returned an error: running callbacks: [Error making glusterfile the default storage class: Error while marking storage class glusterfile as default: Operation cannot 
be fulfilled on storageclasses.storage.k8s.io "glusterfile": the object has been modified; please apply your changes to the latest version and try again]
🌟  Enabled addons: storage-provisioner, kubevirt, default-storageclass, dashboard
🏄  Done! kubectl is now configured to use "minikube" cluster and "" namespace by default


v1.15.1

minikube start --vm=true 
😄  minikube v1.15.1 on Darwin 10.14.6
🆕  Kubernetes 1.19.4 is now available. If you would like to upgrade, specify: --kubernetes-version=v1.19.4
✨  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...
❗  Enabling 'default-storageclass' returned an error: running callbacks: [Error making standard the default storage class: Error while marking storage class standard 
as default: Operation cannot be fulfilled on storageclasses.storage.k8s.io "standard": the object has been modified; please apply your changes to the latest version 
and try again]
🌟  Enabled addons: storage-provisioner, storage-provisioner-gluster, dashboard
🏄  Done! kubectl is now configured to use "minikube" cluster and "" namespace by default

v1.12.3

minikube start --vm=true
😄  minikube v1.12.3 on Darwin 10.14.6
✨  Using the docker driver based on existing profile
❗  Increase Docker for Desktop memory to at least 2.5GB or more:

	Docker for Desktop > Settings > Resources > Memory

❗  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
🔄  Restarting existing docker container for "minikube" ...
🐳  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


Related terms

See also

Advertising: