Unable to install Krew on Linux

[Hector242]

Hello Team,

I'm trying to install Krew on a Linux server, but I got the following error messages.

[root@vts~]# (

set -x; cd "$(mktemp -d)" && OS="$(uname | tr '[:upper:]' '[:lower:]')" && ARCH="$(uname -m | sed -e 's/x8664/amd64/' -e 's/(arm)(64)\?.*/\1\2/' -e 's/aarch64$/arm64/')" && KREW="krew-${OS}${ARCH}" && curl -fsSLO "https://github.com/kubernetes-sigs/krew/releases/latest/download/${KREW}.tar.gz" && tar zxvf "${KREW}.tar.gz" && ./"${KREW}" install krew ) ++ mktemp -d

• cd /tmp/tmp.q0JygZVSfi ++ uname ++ tr '[:upper:]' '[:lower:]'
• OS=linux ++ uname -m ++ sed -e s/x86_64/amd64/ -e 's/(arm)(64)\?.*/\1\2/' -e 's/aarch64$/arm64/'
• ARCH=amd64
• KREW=krew-linux_amd64
• curl -fsSLO https://github.com/kubernetes-sigs/krew/releases/latest/download/krew-linux_amd64.tar.gz
• tar zxvf krew-linux_amd64.tar.gz ./LICENSE ./krew-linux_amd64
• ./krew-linux_amd64 install krew -bash: ./krew-linux_amd64: Permission denied.

Checking the tmp file I noticed that the script file is taking another user as it's owner. However, I did try to change the owner to root, but I'm still getting the same error messages.

[root@vts~]# cd /tmp/tmp.q0JygZVSfi/ [root@vts tmp.q0JygZVSfi]# ls -l total 15980 -rwxr-xr-x. 1 redhat 121 12164162 Dec 31 1999 krew-linux_amd64 -rw-r-----. 1 root root 4186018 Jan 3 17:16 krew-linux_amd64.tar.gz -rw-r--r--. 1 redhat 121 11358 Dec 31 1999 LICENSE [root@vts tmp.q0JygZVSfi]#

Thanks in advance, Best.

[guettli]

I just had the same issue. I think it is related to some security-feature that you are not allowed to execute files from /tmp.

I copied the file to /var/tmp, and there it was executable.

[ahmetb]

I think it is related to some security-feature that you are not allowed to execute files from /tmp.

I'd be interested in what that security feature is. If anyone knows, please add a comment. I am able to do docker run --rm alpine + apk add curl git and install Krew in there just fine. So I assume this is not a standard thing.

[NimbleArchitect]

it sounds like SELinux could be blocking it but without knowing more details like the distribution its hard to guess at

I just clocked the username 'redhat' in the output so I'll take a stab and say its related to a SELinux security policy

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ahmetb]

/close not reproducible. please feel free to open a new issue if you have a clean repro.

[k8s-ci-robot]

@ahmetb: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/krew/issues/752#issuecomment-1219819760): >/close >not reproducible. please feel free to open a new issue if you have a clean repro. Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.