vm-driver=none connection failures after network restart

[jakefeasel]

FEATURE REQUEST

Please provide the following details:

Environment:

Minikube version (use minikube version): v0.25.0

• OS (e.g. from /etc/os-release): "Ubuntu 16.04.3 LTS (Xenial Xerus)"
• VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName): none
• ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION): n/a
• Install tools:
• Others: Docker version 18.02.0-ce

What happened: Install minikube on Linux:

minikube start --vm-driver=none

All is fine initially. However, upon network restart (either from a laptop going to sleep or a full system reboot) the original docker0 interface IP address changes. This causes all connectivity to the cluster to fail with network timeout errors.

What you expected to happen: The connection to the cluster to continue to work through network restarts.

How to reproduce it (as minimally and precisely as possible):

On a linux host:

minikube start --vm-driver=none

reboot host
attempt to use kubectl; observe network timeout failures