Minikube: Shipping KVM2 driver with minikube

Created on 25 Jan 2018  路  11Comments  路  Source: kubernetes/minikube

FEATURE REQUEST

KVM2 needs to be installed separately - https://github.com/kubernetes/minikube/blob/master/docs/drivers.md#kvm2-driver. Why is it impossible to embed it like KVM?

Also, an explanation why KVM2 is better will be welcome.

ckvm2 kinfeature lifecyclstale packaging triagduplicate

Most helpful comment

The KVM and KVM2 drivers are getting merged, so that there is a common and supported "libvirt" driver...

Hopefully this should make for a more smooth installation experience, in the future. Including "qemu" driver.

All 11 comments

yep, same with me, for the kvm-driver either. this is very confusing

Well i have a working solution. It would really help if there is a --test-environment to show which privileges and binaries are needed. like creating networks via virsh, needing docker-machine-driver-kvm2 and so on.

Here's my working solution:

  • debian stretch, purge any virtualbox, install libvirt* packages, these are not any more longer libvirt-bin but packages in different packages and virt-manager is helpful as well. restart for eventual vbox modules.
  • install docker-ce from the community.
  • get docker-machine-driver-kvm2 from the other repository as mentioned in the docs.
  • sudo minikube start --vm-driver=kvm2 # without sudo you can set it up but you WONT get to the pod later in my experience
  • sudo kubectl run hello-minikube --image=k8s.gcr.io/echoserver:1.4 --port=8080

and so on as described in https://kubernetes.io/docs/getting-started-guides/minikube/#quickstart with sudo.

Now that i have a working environment i look into it, which privileges are needed in fact, so i do not need sudo all the time. perhaps it helps someone else.

The KVM and KVM2 drivers are getting merged, so that there is a common and supported "libvirt" driver...

Hopefully this should make for a more smooth installation experience, in the future. Including "qemu" driver.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

/remove-lifecycle stale

The new driver is here: https://github.com/machine-drivers/docker-machine-driver-libvirt

I don't think it has all the fixes from KVM2 in yet though, and it is still being called KVM...

If that's the new driver, where's the old one? I don't see other branches on that repo; yet, the last commit there was a year ago.
Is the kvm2 driver only available as a binary download?

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

This is sort of a dupe of #1623 - but I'll let it be because it's specific.

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

Closing in preference to #1623

Was this page helpful?
0 / 5 - 0 ratings

Related issues

javajon picture javajon  路  3Comments

RaeesBhatti picture RaeesBhatti  路  3Comments

vainikkaj picture vainikkaj  路  3Comments

olalonde picture olalonde  路  3Comments

mrtkp9993 picture mrtkp9993  路  3Comments