Open
Description
~/minikube (master) $ mk delete
π "minikube" profile does not exist, trying anyways.
π Removed all traces of the "minikube" cluster.
~/minikube (master) $ mk start -n 2
π minikube v1.15.1 on Darwin 10.15.7
β¨ Automatically selected the docker driver. Other choices: hyperkit, virtualbox
π Starting control plane node minikube in cluster minikube
π Pulling base image ...
π₯ Creating docker container (CPUs=2, Memory=2200MB) ...
E1124 10:22:03.958407 70271 network_create.go:77] error while trying to create network create network minikube 192.168.49.0/24: docker network create --driver=bridge --subnet=192.168.49.0/24 --gateway=192.168.49.1 -o --ip-masq -o --icc --label=created_by.minikube.sigs.k8s.io=true minikube -o com.docker.network.driver.mtu=1500: exit status 1
stdout:
stderr:
Error response from daemon: network with name minikube already exists
β Unable to create dedicated network, this might result in cluster IP change after restart: un-retryable: create network minikube 192.168.49.0/24: docker network create --driver=bridge --subnet=192.168.49.0/24 --gateway=192.168.49.1 -o --ip-masq -o --icc --label=created_by.minikube.sigs.k8s.io=true minikube -o com.docker.network.driver.mtu=1500: exit status 1
stdout:
stderr:
Error response from daemon: network with name minikube already exists
^C
~/minikube (master) $ docker network rm minikube
minikube
~/minikube (master) $ mk delete
π₯ Deleting "minikube" in docker ...
π₯ Deleting container "minikube" ...
π₯ Removing /Users/selgamal/.minikube/machines/minikube ...
π Removed all traces of the "minikube" cluster.
~/minikube (master) $ mk start -n 2
π minikube v1.15.1 on Darwin 10.15.7
β¨ Automatically selected the docker driver. Other choices: hyperkit, virtualbox
π Starting control plane node minikube in cluster minikube
π₯ Creating docker container (CPUs=2, Memory=2200MB) ...
π³ Preparing Kubernetes v1.19.4 on Docker 19.03.13 ...
π Verifying Kubernetes components...
π Enabled addons: storage-provisioner, default-storageclass
β Multi-node clusters are currently experimental and might exhibit unintended behavior.
π To track progress on multi-node clusters, see https://github.com/kubernetes/minikube/issues/7538.
π Starting node minikube-m02 in cluster minikube
π₯ Creating docker container (CPUs=2, Memory=2200MB) ...
π Found network options:
βͺ NO_PROXY=192.168.59.2
π³ Preparing Kubernetes v1.19.4 on Docker 19.03.13 ...
βͺ env NO_PROXY=192.168.59.2
π Verifying Kubernetes components...
π Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default