This is not a bug but improvement request/suggestion: Is there any reason why minikube ebuild does not build/distribute localkube binary? In case we distribute it minikube will not require to download it at start and put somewhere at /usr/local. This will keep system more clean of non-package binaries. However it will require from user to use "--kubernetes-version file:///usr/bin/localkube" extra arg to minikube at start (otherwise it will download it). If I understand right it is required only for "--vm-driver=none" mode, so maybe it is reasonable to have appropriate USE flag? I tested it on my setup and it works fine, it doesn't require any extra deps. One more question: Is is possible to provide post-merge info with explicit list of kernel options required (but not set). e.g. like we have for docker? In fact minikube extensively uses iptables which depends on lots of stuff from kernel's netfilter and costs me quite some time to figure out what is missing in kernel. Thanks, let me know if you need more info from me?
I've added the localkube binary back to minikube-0.28.0-r1
