I am not so much into developing for Windows, nor do I have any clue how Windows names pipes work. But as I understand this tool, it uses the possiblity to run both Linux and Windows binaries in the WSL. So with socat the WSL-side socket is read and with npiperelay.exe being a Windows executable this is the bridge to pipe into the Windows socket.
I would like to use my Windows ssh-agent in a Docker container. which we use as a common development environment (VSCode Remote). But as with your approach the Windows binary is the bridge, this cannot be used straight forward for my use case.
Do you see a chance, that the pipe could be relayed through an http tunnel or any other ways?
Hi,
I am not so much into developing for Windows, nor do I have any clue how Windows names pipes work. But as I understand this tool, it uses the possiblity to run both Linux and Windows binaries in the WSL. So with
socat
the WSL-side socket is read and withnpiperelay.exe
being a Windows executable this is the bridge to pipe into the Windows socket.I would like to use my Windows ssh-agent in a Docker container. which we use as a common development environment (VSCode Remote). But as with your approach the Windows binary is the bridge, this cannot be used straight forward for my use case.
Do you see a chance, that the pipe could be relayed through an http tunnel or any other ways?