none driver: minikube shouldn't write binaries to /usr/bin

[tstromberg]

With the none driver, minikube will overwrite the following system paths:

• /usr/bin/kubeadm - Updated to match the exact version of Kubernetes selected
• /usr/bin/kubectl - Updated to match the exact version of Kubernetes selected

Basically, anywhere else is better, but to write directly to /usr/bin feels yucky. It'd be nicer to write the binaries somewhere else, preferably but not necessarily versioned. For instance:

$XDG_CACHE_HOME/minikube/binaries/kubeadm-v1.13.0

Or:

/usr/local/minikube/kubeadm-v1.13.0

[afbjorklund]

I think it is perfectly reasonable to install kubeadm to the default /usr/bin location.
The same thing happens, if you install it from an .rpm and a .deb for instance ?

https://kubernetes.io/docs/setup/independent/install-kubeadm/#installing-kubeadm-kubelet-and-kubectl

After all, the VM you give to minikube is dedicated to running kubernetes on.
You are not giving it something important - like directly on your laptop, right ? ;-)

https://github.com/kubernetes/minikube/blob/master/docs/vmdriver-none.md

[afbjorklund]

Could install to /usr/local/bin, but I'm not sure that would help anything.

[afbjorklund]

With the none driver, minikube will overwrite the following system paths:

• /usr/bin/kubeadm - Updated to match the exact version of Kubernetes selected
• /usr/bin/kubectl - Updated to match the exact version of Kubernetes selected

You probably mean "/usr/bin/kubelet" here ? We don't install kubectl - yet.

[tstromberg]

Using /usr/bin violates both user expectations and the LSB/FHS standards: https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s09.html

The main user expectation violated is that we may be overwriting system binaries.

Storing files in /usr/bin also conflicts with the goal of reducing/removing usage of 'minikube' by the root user: #3138

[afbjorklund]

@tstromberg : I guess I am still thinking about the old/existing implementation, when you run sudo -E minikube start --vm-driver=none locally on your dedicated VM - rather than the new version of actually running it on the same machine as the 'kubectl` like your laptop or so. When running locally, it makes sense to not overwrite system binaries and to run minikube without root (by it using sudo where it is needed).

Maybe we could use the binaries straight off the cache, rather than copying them to a temp location ?
~/.minikube/cache/v1.13.0/kubeadm vs ~/.cache/minikube/binaries/kubeadm-v1.13.0

[MatejLach]

Is there a workaround for now?