Package Details: docker-machine-driver-kvm2 1.27.0-1

Git Clone URL: https://aur.archlinux.org/docker-machine-driver-kvm2.git (read-only, click to copy)
Package Base: docker-machine-driver-kvm2
Description: Minikube-maintained KVM driver for docker-machine
Upstream URL: https://minikube.sigs.k8s.io
Keywords:
Licenses: Apache
Submitter: hokesau6
Maintainer: tiny
Last Packager: tiny
Votes: 20
Popularity: 0.000006
First Submitted: 2017-12-19 02:18 (UTC)
Last Updated: 2022-09-19 06:44 (UTC)

Latest Comments

1 2 Next › Last »

bouk commented on 2018-11-01 16:48 (UTC)

I needed to install ebtables, qemu-headless, and start libvirtd to make minikube work with this package. Basically I followed these instructions: http://blog.programmableproduction.com/2018/03/08/Archlinux-Setup-Minikube-using-KVM/

kketch commented on 2018-09-26 15:23 (UTC)

@braderhart I'm confused I actually had to reinstall ebtables, because libvirt use it

kketch commented on 2018-09-24 11:35 (UTC)

the ebtables dependency needs to be changed to iptables

saulius_vl commented on 2018-04-23 08:24 (UTC)

@braderhart: works perfectly now, thanks! :)

saulius_vl commented on 2018-04-22 08:10 (UTC)

@braderhart: pretty sure the issue is that the PKGBUILD source directive downloads a non-versioned binary, so if the pacaur cache already contains a previous version it skips downloading the new binary and checks the updated sha256hash against the old binary. The source should probably be prefixed with a versioned name, something like https://github.com/larte/kubectl-bin/blob/master/PKGBUILD#L15.

It's happening again with the latest update, clearing the old binary from the cache fixes the problem.

saulius_vl commented on 2018-03-30 06:36 (UTC)

@braderhart: this happens when updating from 0.25.0-1, a clean install or clearing the pacaur cache & rebuilding works. Could the problem be that the extracted binary "docker-machine-driver-kvm2" is not versioned ?