-
Notifications
You must be signed in to change notification settings - Fork 923
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
Windows 10 WSL - "cannot allocate memory" when calling a plugin #603
Comments
Here's a |
I am also having issue installing Krew on Windows and got here from kubernetes-sigs/krew#156
I tried different plugins but same error. kubectl version is this:
Windows version: Microsoft Windows Server 2012 R2 Datacenter |
kubectl calls Exec which on windows returns error (https://golang.org/src/syscall/exec_windows.go) |
Also getting
Ran the following command in an elevated PowerShell and it installed successfully:
kubectl version:
Windows version: Windows 10 Pro Got here from kubernetes-sigs/krew#156 Installed krew version: https://github.com/kubernetes-sigs/krew/releases/tag/v0.2.1 |
/sig cli |
I just updated to Windows 10 1903 (10.0.18362) and can no longer reproduce this under WSL. Can anyone else confirm? |
@spacecat, are you still seeing this?
EDIT: I see the fix for this bug is in the 1.16 branch. Never mind, I spoke too soon. |
Updating Windows 10 did not fix the issue for me. Still getting |
Experiencing this under Windows 10 (10.0.17763) and kubectl 1.19, getting |
me too for |
Windows 10 1809 and WSL1, most of krew calls I get "cannot allocate memory". I'm using ConEmu terminal. |
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): no
What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): windows; allocate
Is this a BUG REPORT or FEATURE REQUEST? (choose one): bug report
Kubernetes version (use
kubectl version
):Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:08:12Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Environment:
uname -a
):Linux DESKTOP-3I1L0FQ 4.4.0-17763-Microsoft #253-Microsoft Mon Dec 31 17:49:00 PST 2018 x86_64 x86_64 x86_64 GNU/Linux
What happened:
kubectl often returns
cannot allocate memory
instead of executing a plugin. Calling the plugin directly always works.What you expected to happen:
calling the plugin via kubectl to work as if called directly
How to reproduce it (as minimally and precisely as possible):
Use the example plugin from https://kubernetes.io/docs/tasks/extend-kubectl/kubectl-plugins/#example-plugin
kubectl often returns
cannot allocate memory
instead of executing the plugin.executing the plugin directly always works
Anything else we need to know:
This also happens with windows compatible plugins when called directly from Windows 10, rather then WSL; however it's easier for me to provide details using linux tooling.
Here's a
strace -o kubectl -ff -y kubectl foo version
kubectl.zip
The text was updated successfully, but these errors were encountered: