use gvisor-tap-vsock binaries directly

[sakai135]

The main changes made to gvisor-tap-vsock for use in wsl-vpnkit was upstreamed back to gvisor-tap-vsock. This allows wsl-vpnkit to use the binaries from gvisor-tap-vsock directly.

• use binaries from gvisor-tap-vsock directly
  • connect over stdio containers/gvisor-tap-vsock#177
  • set proper protocol for stdio containers/gvisor-tap-vsock#195
• remove DHCP - also resolves issue with DHCP overriding resolv.conf in standalone mode
• replace the service script with systemd - officially supported method of running services
• remove the config file in the Windows host
• added checks on resolv.conf and Windows executable
• added distro builds with ubuntu and fedora to test standalone script

[scratchmex]

Is there anything I can help to getting this merged and released? I'm having the same problems as the linked issue.

[sakai135]

@scratchmex I'm actually waiting for gvisor-tap-vsock to cut a new release so I can just pull the binaries instead of compiling it here.

If you'd like to try this branch, you can build the branch or download wsl-vpnkit.tar.gz from the build artifacts and follow the updated readme doc. I would appreciate any feedback.

[gbraad]

I'm actually waiting for gvisor-tap-vsock to cut a new release

Sorry about this. I think this needs to be sped up. @cfergeau was looking into containers/gvisor-tap-vsock#161, to make that part of a new release. I think we should make an intermediate first.

[gbraad]

@sakai135 https://github.com/containers/gvisor-tap-vsock/releases/tag/v0.6.0 is available now; Thanks @cfergeau ;-)

[sakai135]

There's an issue with v0.6.0 regarding a conflict with the stdio code upstreamed and a later PR. Submitted containers/gvisor-tap-vsock#195 to fix the issue.

Updated this PR branch to build gvisor-tap-vsock from the fix branch for now.

[cfergeau]

I've cut a 0.6.1 gvisor-tap-vsock release with your fix