@@ -56,53 +56,76 @@ If a sudor other than ubuntu is used, move the following two directories::
Exercise 0.0: Starting Minikube
-------------------------------
Start Minikube without a hypervisor (a.k.a Docker runtime)::
Start Minikube with Docker::
sudo minikube start --vm-driver=none
minikube start --vm-driver='docker'
The following message should be displayed when Minikube is started successfully::
😄 minikube v1.0.1 on linux (amd64)
🔥 Creating none VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
📶 "minikube" IP address is 10.0.0.5
🐳 Configuring Docker as the container runtime ...
🐳 Version of container runtime is 18.09.2
✨ Preparing Kubernetes environment ...
❌ Unable to load cached images: loading cached images: loading image /home/ubuntu/.minikube/cache/images/gcr.io/k8s-minikube/storage-provisioner_v1.8.1: stat /home/ubuntu/.minikube/cache/images/gcr.io/k8s-minikube/storage-provisioner_v1.8.1: no such file or directory
💾 Downloading kubeadm v1.14.1
💾 Downloading kubelet v1.14.1
🚜 Pulling images required by Kubernetes v1.14.1 ...
🚀 Launching Kubernetes v1.14.1 using kubeadm ...
⌛ Waiting for pods: apiserver proxy etcd scheduler controller dns
🔑 Configuring cluster permissions ...
🤔 Verifying component health .....
🤹 Configuring local host environment ...
⚠️ The 'none' driver provides limited isolation and may reduce system security and reliability.
# It is a good idea to create a plan first. The input values can be provided with var-files.
#
terraform plan -lock=false-var-file"${DIR}/resops.tf"-out"${DIR}/kubespray/out.plan""${DIR}/kubespray/contrib/terraform/openstack"
# -lock=false
terraform plan -var-file"${DIR}/resops.tf"-out"${DIR}/kubespray/out.plan""${DIR}/kubespray/contrib/terraform/openstack"
# Apply the changes planned explicitly. Terraform does not guarantee plan and apply generates the same plan. Thus, it is a good idea to provide an explicit plan and turn on the auto approval.