Replies: 1 comment
-
@tr4l You're right, I'm using the stdin/out integration in WSL to communicate between WSL and Windows. I got that idea from Docker for Windows, so credits go to that team. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I'm wondering how the tunneling between the host and the guest is done (on version 0.3x).
Looking at the doc, it seems that you use gvisor-tap-vsock for that purpose, and that project use Qemu, Hyperkit, Hyper-V and User Mode Linux. BTW I discovered vsock which seems amazing.
Looking more in details, I've seen that you wrote your own transport
Let me know if I'm correct now.
The transport you wrote use a feature of WSL which allow to run windows executable, on WSL console and "shared" the console.
The executable is run under windows context (so have access to windows network), and the output on the console can be seen on the wsl. With that you "just" wrap standard input and output of the console to communicate.
If this is correct, this is a gernius move.
Beta Was this translation helpful? Give feedback.
All reactions