Summary: | sys-cluster/minikube-0.25.0 should have alternative vm-drivers available | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Renich Bon Ciric <renich> |
Component: | Current packages | Assignee: | Manuel Rüger (RETIRED) <mrueg> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | holger |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Renich Bon Ciric
2018-03-06 18:29:50 UTC
Ah! Just found out that docker-machine-kvm exists in portage; just not docker-machine-kvm2. Maybe it's just a matter of updating that one and adding a soft dependency? (In reply to Renich Bon Ciric from comment #1) > Ah! Just found out that docker-machine-kvm exists in portage; just not > docker-machine-kvm2. Maybe it's just a matter of updating that one and > adding a soft dependency? I struggled with the same problems and came up with bug #660304 - please contribute if you know how to make the kvm thingy work, I'd love to stop using vbox! (In reply to Holger Hoffstätte from comment #2) > I struggled with the same problems and came up with bug #660304 - > please contribute if you know how to make the kvm thingy work, > I'd love to stop using vbox! I think you just need to set it to use kvm2, no? I have these settings. They might help: $ cat .minikube/config/config.json { "WantReportError": true, "coredns": true, "cpus": 8, "heapster": true, "ingress": true, "memory": 16000, "metrics-server": true, "vm-driver": "kvm2" } Please check with recent version of minikube and report back if this issue still exists. |