Skip to content

minikube delete doesn't always delete the docker networkΒ #9776

Open
@sharifelgamal

Description

@sharifelgamal
~/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

Metadata

Metadata

Assignees

Labels

co/docker-driverIssues related to kubernetes in containerkind/bugCategorizes issue or PR as related to a bug.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/backlogHigher priority than priority/awaiting-more-evidence.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions