-
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 install fails on Ubuntu WSL (Windows Subsystem for Linux) #159
Comments
See #156. |
I reviewed that ticket before opening and I do not think they are the same. |
@StianOvrevage The issue is with the length of the underlying NTFS path of the WSL root directory, whose mount defaults to deep in your windows profile. With the additional krew folder depth and long length of the folder name, the full path exceeds the Windows MAX_PATH length of 260. I worked around the issue by moving my /home mount to a directory in the root of C: This is using the WSL Ubuntu image: /etc/fstab /etc/wsl.conf |
@StianOvrevage can you give an example of a full path exceeding MAX_PATH? I'm curious how it looks like witht he additional krew folder depth. |
Great job figuring this out! I was not able to get automatic mounting of I did however just mount |
If any of you could write up summary a summary of the WSL issue, I would like to link to it from the README>Installation section as a "Known issue with WSL". |
@ahmetb I don't know enough about WSL to actually find the underlying path as mapped to the NTFS disk. According to https://blogs.msdn.microsoft.com/wsl/2016/06/15/wsl-file-system-support/ at some point it was at |
|
@StianOvrevage wsl.conf doesn't exist by default, you can just create it. @ahmetb The full patch for me is only 214, now that I actually counted. What's odd is that it is a permission error and I traced all the system calls and they looked fine from a user permissions stand-point. It could just be a bad error message. It was a bit for naught anyway, pending this fix for kubectl executing plugins in WSL: |
This Worked for me, But I don't want to move my /home directory, so I created dir
|
@alioSHA512 Good to hear. You can also set |
Tried as root and non-root. Both fails with same error.
The text was updated successfully, but these errors were encountered: