Skip to content

Conversation

kosmoit
Copy link

@kosmoit kosmoit commented Mar 6, 2020

so that the minikube start command works (with this current setup fo tube-start.sh)

when user not in the group, after rebooting and running the minikube start command, they will receive the following message:
'kvm2' driver reported an issue: /usr/bin/virsh domcapabilities --virttype kvm failed:
error: failed to connect to the hypervisor
error: authentication unavailable: no polkit agent available to authenticate action 'org.libvirt.unix.manage'

IF this occurs, the only way to resolve is minikube delete, and to add the suer to the libvirt group command before trying again.

so that the minikube start command works (with this current setup fo tube-start.sh)

when user not in the group, after rebooting and running the minikube start command, they will receive the following message:
'kvm2' driver reported an issue: /usr/bin/virsh domcapabilities --virttype kvm failed:
error: failed to connect to the hypervisor
error: authentication unavailable: no polkit agent available to authenticate action 'org.libvirt.unix.manage'

IF this occurs, the only way to resolve is minikube delete, and to add the suer to the libvirt group command before trying again.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant