-
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
Fedora: "dnf install minikube" installs gzip file instead of ELF binary #3020
Comments
I have no idea what that repo is, but the bug seems to be a packaging error in that process. Where did you find that link? |
Hi Sir, From this link : https://github.com/kubernetes/minikube, then ==> Other ways to install and click on Fedora/CentOS/Red Hat COPR. You will reach the page https://copr.fedorainfracloud.org/coprs/antonpatsev/minikube-rpm/ and then click on the link Fedora27, downloads repo. In /etc/yum.repos.d on my machine, I've create a file minikube-rpm-fedora-27.repo with this content 👍 hint : when issuing this command : file /usr/local/bin/minikube I have this message : minikube: gzip compressed data, was "minikube-linux-amd64", last modified: Thu Nov 30 16:34:47 2017, max compression I was expecting a message like this : ELF 64-bit LSB executable, x86-64, Please help |
I'd probably contact the maintainer of this package (antonpatsev) - the Fedora package is likely to be junk. I'll have to install a Fedora host to confirm. Looking at https://copr.fedorainfracloud.org/coprs/antonpatsev/minikube-rpm/packages/ - it's still at minikube 0.24, which is quite old anyways. |
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. |
That COPR repo is outdated and not very high quality. There are other similar COPR repos that just copy the precompiled binary. Instead, I would recommend just following the build instructions I've put on my site: #!/bin/bash
# libvirt-devel is required for building docker-machine-driver-kvm2
sudo dnf install glibc-static libvirt-devel
export GOPATH=$(go env GOPATH)
export GOBIN=$GOPATH/bin
# go get will not work here, minikube expects to have a certain directory structure
if [ -n "$(find $GOPATH/src/k8s.io/minikube -maxdepth 0 -empty)" ]
then
git clone https://github.com/kubernetes/minikube.git $GOPATH/src/k8s.io/minikube
fi
cd $GOPATH/src/k8s.io/minikube
git checkout -- .
git checkout $(git describe --abbrev=0 --tags)
make clean
make && make drivers
cp out/minikube $GOBIN
cp out/docker-machine-driver-kvm2 $GOBIN This will checkout the latest tag, build and put it in diff --git a/Makefile b/Makefile
index 42b571bfd..8da3cf0b1 100755
--- a/Makefile
+++ b/Makefile
@@ -173,7 +173,7 @@ depend: out/minikube.d out/test.d out/docker-machine-driver-hyperkit.d out/stora
all: cross drivers e2e-cross
.PHONY: drivers
-drivers: out/docker-machine-driver-hyperkit out/docker-machine-driver-kvm2
+drivers: out/docker-machine-driver-kvm2
.PHONY: integration
integration: out/minikube Feel free to make your own COPR repo based off these instructions, but I have no interest in maintaining an RPM myself. |
Closing, since that repo isn't managed by us - still hasn't updated past 0.24! |
Wouldn't it be more appropriate to keep it open until, i.e there's a PR that either removes the link or changes it to a more up-to-date repo? That is, the README currently links to said outdated repo. |
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
My computer :
xxxx@localhost yum.repos.d]# uname -a
Linux localhost.localdomain 4.17.7-100.fc27.x86_64 #1 SMP Tue Jul 17 16:29:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
I've minikube installed on my PC from https://copr.fedorainfracloud.org/coprs/antonpatsev/minikube-rpm/repo/fedora-27/antonpatsev-minikube-rpm-fedora-27.repo
xxxx@localhost yum.repos.d]# which minikube
/usr/local/bin/minikube
I can't run the commant : minikube start
xxxx@localhost yum.repos.d]# minikube version
-bash: /usr/local/bin/minikube : impossible to execute the binary file : Exec format error
Please, help !
The text was updated successfully, but these errors were encountered: