-
Notifications
You must be signed in to change notification settings - Fork 369
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
Krew installation fails on Windows 10 #156
Comments
Not a known issue. But if you search for “A required privilege is not held by the client.“ it seems like it’s a machine issue. Perhaps something like a policy is preventing you. |
@ahmetb it looks like creating a symlink is requiring special permissions on the machine (golang/dep#773 is similar). I do not have those. Is it possible to have a switch to copy the files instead of creating a symlink? Can I solve this manually? What do I need to copy where? |
I think we tried this on windows and it was working. Do you have any data points on
The error shows you the two paths you need to copy. Copy the one in .krew\store... to .krew\bin... path that's listed in the error. |
@ahmetb Which is the second path are you referring to? I have copied I added the folder kubectl plugin list shows no plugins though: |
Try installing any kubectl plugin without krew and see if that works. Right now you're potentially reporting a kubectl bug (issues with the plugin mechanism) and this is not the correct repo for that. |
Is it manifest= or source= ? The installation instructions (https://github.com/GoogleContainerTools/krew/blob/v0.2.1/README.md) specifies 'source' but it fails on windows with the error "F0304 20:06:42.638733 1884 root.go:52]unknown flag: --source" Edit: It works with manifest, but once installed, it shows the error: |
Should be --manifest. I think the readme was wrong so it’s changed post-v0.2.1. |
I'm having the same problem (on Windows 10 directly and with WSL)
and here's a partial strace
a manual installation seems to work, but I seem to hit some other incompatibility?
|
@jon-walton thanks for detailing these out. I think this is a legit bug. I'm surprised Go's os.Symlink code did not work on native Windows execution. In your case I'm seeing the installation error is actually different:
Similarly, the Can you provide strace for I'm gonna keep this open for tracking. I have no idea on where to start, or a windows machine to try things right now. Any contributions/help welcome. |
@ahmetb There's not much to talk about with
What's interesting, is this seems to be intermittent? but once the
Here's a strace of
the
If I run as for running on Windows directly...
c:\tools\kubectl-krew.exe
k version --client PS C:\Users\jonwa> k krew --help 😕 |
Ditto for me on WSL ubuntu and on win 10. |
A quick follow up. If I run krew-install in an administrative powershell prompt, it installs but I get the same
|
I don't think the installing https://github.com/jordanwilson230/kubectl-plugins
@juv I also received the error |
this seems to definitely be a kubectl issue?
|
@jon-walton do you mind opening an issue to https://github.com/kubernetes/kubectl with a minimal repro with one of those plugins (ideally without mentioning krew, since it's not a krew issue). |
opened kubernetes/kubectl#603 . it also repros with the example foo plugin |
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. |
/close |
@ahmetb: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I followed the instructions in the readme to install Krew on Windows.
I get the following error:
I also tried with
.\krew-windows_amd64.exe install --manifest="C:\Development\K8s\krew\krew.yaml" --archive="C:\Development\K8s\krew\krew.zip"
, same error.Is there anything I'm missing?
The text was updated successfully, but these errors were encountered: