Closed deknos closed 3 years ago
Hello,
Can you describe what issues you're facing ? Minikube is happy here.
$ which minikube
/home/dir/.binenv/minikube
$ minikube start
π minikube v1.14.2 sur Ubuntu 20.04
...
π Pulling base image ...
πΎ Downloading Kubernetes v1.19.2 preload ...
> preloaded-images-k8s-v6-v1.19.2-docker-overlay2-amd64.tar.lz4: 486.33 MiB
π₯ Creating docker container (CPUs=2, Memory=16000MB) ...
...
π Verifying Kubernetes components...
π Enabled addons: storage-provisioner, default-storageclass
π Done! kubectl is now configured to use "minikube" by default
$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
minikube Ready master 25s v1.19.2
Here:
user01@testvm:~$ minikube start --driver=none
π minikube v1.17.1 auf Ubuntu 20.04 (vbox/amd64)
β¨ Using the none driver based on user configuration
π€· Exiting due to PROVIDER_NONE_NOT_FOUND: The 'none' provider was not found: running the 'none' driver as a regular user requires sudo permissions
user01@testvm:~$ sudo minikube start --driver=none
[sudo] Passwort fΓΌr benutzer01:
sudo: minikube: Befehl nicht gefunden
user01@testvm:~$
This might work:
sudo env "PATH=$PATH" "HOME=$HOME" minikube start --driver=none
I do not see any easier safe global solution to this.
A global binenv mode where binaries & configs would be shared for the entire system would solve this, but is not really in the plans right now.
EDIT: there is also the option of installing binenv for the root user.
This looks good enough, perhaps you should mention it in the documentation, at least that works for me :)
sadly you only can use it then as root, not as non-root when you install it with root in /usr/local/bin :D
Hello, i start after a while stumbling often enough with sudo and tools i installed with binenv. Can you add a documentation which best practice you would recommend, so tools are usable with sudo? because otherweise minikube for example is not really usable