-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make a release and some installation instructions #8
Comments
We will not make releases for the moment. Not until CI and tests exists and
people other than us take this responsibility. We only consume this as a
library for now...
…On Sun, Sep 9, 2018, 16:32 Anders Björklund ***@***.***> wrote:
Seems like we need a v0.1.1 binary built, with some matching lines in the
README.md afterwards.
$ curl -L https://github.com/machine-drivers/docker-machine-driver-qemu/releases/download/v0.1.0/default.docker-machine-driver-qemu-$(uname -s)-$(uname -m) > docker-machine-driver-qemu
$ sudo cp docker-machine-driver-qemu /usr/local/bin/docker-machine-driver-qemu
$ sudo chmod 755 /usr/local/bin/docker-machine-driver-qemu
Not sure where that "default" came from last time, but we should probably
try to get rid of it if we can ?
Will also fix #2
<#2>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#8>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAHZvXQxkpU1gN605_4zH4-tzPZ_LsLks5uZNIggaJpZM4WgMmw>
.
|
@gbraad: sure you mean qemu too, and not only kvm (libvirt) ? Maybe same applies to all drivers... Anyway, I still have to look up what build system @SvenDowideit used for making the https://github.com/machine-drivers/docker-machine-driver-qemu/releases/tag/v0.1.0 I just built the binaries on the host, which worked fine since there are no libvirt dependencies here. |
This was the previous build I made: docker-machine-driver-qemu-bab75de.linux-amd64.tar.gz |
Seems like we need a
v0.1.1
binary built, with some matching lines in the README.md afterwards.Not sure where that "default" came from last time, but we should probably try to get rid of it if we can ?
Will also fix #2
The text was updated successfully, but these errors were encountered: