Hi @medyagh, I added a small test (TestNeedsSudo) to verify which drivers require sudo. Here are the results I got:

NeedsSudo = true: podman, none, virtualbox, hyperkit, vmware, parallels, krunkit, hyperv, vfkit

Where did you get this info?

podman does not require sudo, this is is is one of its main features compared to docker
vfkit does not require sudo
krunkit does not require sudo

NeedsSudo = false: docker, kvm2, qemu2, ssh

docker requires sudo for installation, but it does not require sudo if add your self to the right group
kvm2 requires sudo to install libvirt, but it does not require sudo if add your self to the libvirt group

Could you please confirm if my test results are correct?

Looks wrong, but the issue is that it is not clear what "requires sudo" means. If it means can I install and use the driver on a system without sudo, then this is not useful metric. sudo (or similar tools like doas) as part of the system. I think the a useful meaning is if we need to use sudo to start a minikube cluster.

Almost everything related to virtualization and networking requires sudo to setup. Once you do the initial setup. you don't need sudo to use the infrastructure. If you don't need sudo it means you are using a crappy user networking solution, which is not what you want to use.

More details on the drivers I know more about:

kvm

status: preferred driver
install: requires sudo do install libvirt. The libvirt daemons runs as root.
configuration: requires sudo to add yourself to the libvirt group
usage: sudo not required

vfkit

status: preferred driver
install: does not requires sudo (.e.g. brew install vfkit)
configuration: to use --network shared sudo required to install vmnet-helper and configure it to run without a password.
usage: sudo not required
- on some managed systems sudo configuration is broken and minikube uses interactive sudo to start vment-helper with sudo

krunkit

status: experimental
install: does not requires sudo (.e.g. brew install krunkit)
configuration: to use --network shared sudo required to install vmnet-helper and configure it to run without a password.
usage: sudo not required
- on some managed systems sudo configuration is broken and minikube uses interactive sudo to start vment-helper with sudo

Check if we have Sudo Permission, if not Lower The priority of the drivers that Need Sudo #21633

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions