Skip to content
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

Closed
enzo1004 opened this issue Jul 25, 2018 · 7 comments
Closed
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. os/linux packaging/rpm Red Hat/Fedora (rpm) packaging issues packaging Packaging issues triage/unresolved Indicates an issue that can not or will not be resolved.

Comments

@enzo1004
Copy link

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 !

@dlorenc
Copy link
Contributor

dlorenc commented Jul 26, 2018

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

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?

@enzo1004
Copy link
Author

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 👍
antonpatsev-minikube-rpm]
name=Copr repo for minikube-rpm owned by antonpatsev
baseurl=https://copr-be.cloud.fedoraproject.org/results/antonpatsev/minikube-rpm/fedora-$releasever-$basearch/
type=rpm-md
skip_if_unavailable=True
gpgcheck=1
gpgkey=https://copr-be.cloud.fedoraproject.org/results/antonpatsev/minikube-rpm/pubkey.gpg
repo_gpgcheck=0
enabled=1
enabled_metadata=1
~
then I used the command : sudo dnf install minikube.

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

@tstromberg tstromberg changed the title minikube start : Exec format error Fedora: "dnf install minikube" installs gzip file instead of ELF binary Sep 18, 2018
@tstromberg tstromberg added os/linux packaging Packaging issues labels Sep 18, 2018
@tstromberg
Copy link
Contributor

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.

@tstromberg tstromberg added packaging/rpm Red Hat/Fedora (rpm) packaging issues kind/bug Categorizes issue or PR as related to a bug. labels Sep 19, 2018
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2018
@ghost
Copy link

ghost commented Dec 28, 2018

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 $GOBIN, which you should add to your $PATH. You may also need to apply this patch:

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.

@tstromberg tstromberg added the triage/unresolved Indicates an issue that can not or will not be resolved. label Jan 24, 2019
@tstromberg
Copy link
Contributor

Closing, since that repo isn't managed by us - still hasn't updated past 0.24!

@ghost
Copy link

ghost commented Jan 24, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. os/linux packaging/rpm Red Hat/Fedora (rpm) packaging issues packaging Packaging issues triage/unresolved Indicates an issue that can not or will not be resolved.
Projects
None yet
Development

No branches or pull requests

5 participants