-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Debian package should include the kvm driver (docker-machine-driver-kvm2) #2982
Comments
+1, I second this. |
+1 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
I suppose removing the .deb altogether is another option ? Then it could be packaged properly downstream instead, using PPA or some similar means. And then wouldn't have to defend the lack of .rpm etc (#402) |
If we packaged kvm2 as debs, maybe that could avoid versioning issues: #3437 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle rotten This is still very desirable for Debian-based systems. |
@mgabeler-lee-6rs : note that virtualbox is still the default driver Added some .deb packaging now, but it is not a hard dependency We could add it as a soft: |
Given vbox as the default driver, Thanks for this! |
Most likely we will need to set up our own apt repository for this to work... Similar to what is available for kubeadm (but not for curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -
cat <<EOF >/etc/apt/sources.list.d/kubernetes.list
deb https://apt.kubernetes.io/ kubernetes-xenial main
EOF See #3110
Currently there is a bug (#4555), so it bypasses docker and uses host. ☹ Update: fixed! Now building properly towards libvirt 1.3.1, so it works "everywhere" FROM gcr.io/gcp-runtimes/ubuntu_16_0_4 |
It's a great idea. |
Linking the conversation in #wg-k8s-infra, so that context doesn't get lost on apt/yum repos: https://kubernetes.slack.com/archives/CCK68P2Q2/p1562665049225800 |
@justaugustus : thanks for the link, but wasn't sure about the full context of the request We will start producing the packages for next release, so there should be some made for 1.3.0 |
Packages are now available: https://storage.googleapis.com/minikube/releases/v1.3.0/docker-machine-driver-kvm2_1.3.0.deb https://storage.googleapis.com/minikube/releases/v1.3.0/docker-machine-driver-kvm2-1.3.0.rpm No support for apt or yum yet. |
Is this a BUG REPORT or FEATURE REQUEST?: FEATURE REQUEST
The minikube-XXX-.deb package is intended to be used on debian systems. To simplify setup and usage of kvm2 driver, it could be include within the package (maybe provided through private debian repository). Thus the installation and upgrade of minikube will be more convenient.
Please provide the following details:
Environment: Linux
Minikube version: 0.27 and 0.28
What happened:
I need to install and maintain (upgrade) docker-machine-driver-kvm2 manually as sudoer.
What you expected to happen:
Installing/upgrading the minikube through debian package, the docker-machine-driver-kvm2 is installed/upgraded accordingly.
The text was updated successfully, but these errors were encountered: