Re:Free up space (effortlessly) on WSL2
by olivermuty on Tuesday August 19, 2025 @01:08AM
(#44948437)
No such thing needez, just alias ssh to ssh.exe and ssh-add to ssh-add.exe and it works out of the box.
aliasing the ssh.exe generally works, but not for all applications. I had issues with this approach while running ansible playbooks ("getsockname failed: Not a socket").
Re:Free up space (effortlessly) on WSL2
by ycombinatrix on Tuesday August 19, 2025 @02:17AM
(#44948749)
You can actually run the windows ssh.exe binary directly from WSL, no extra setup needed. Give it a try.
I used to use the `npiperelay` method but have since switched to this and it works nicely.
Re:Free up space (effortlessly) on WSL2
by mikepurvis on Tuesday August 19, 2025 @07:53AM
(#44950572)
I’m aware that 1P themselves recommend this but I don’t like it; a lot of my usage is other things like git or docker or ansible calling ssh and I don’t want to deal with those things having to also be steered to an alternative ssh implementation.
I can confirm npiperelay does the job just fine.
If you happen to use Nix, I have a quick and easy package at github:Cu3PO42/gleaming-glacier/next#wsl-ssh-agent. Simply install that and 'source $(which wsl-ssh-agent)' in your bashrc and you should be good to go. (There's also a HM module in the Flake.)
My biggest frustration with WSL at present is that 1Password won’t properly support proxying their ssh agent into it.