[600frogs]

Your set-up sounds exactly what I'm after - from my comment to a different reply:

> I think my end goal is to have a contained development environment whilst not being forced to use specific tools (i.e. VSCode remote debugging, eugh) and not sacrificing compilation times by running in a VM that's too slow.

Are there any other gotchas to working like this? As it happens I'm a go dev using GoLand so your go-specific issues are of interest to me. I'm not too bothered about not being able to use Windows GoLand as I'd be just using it from WSL2 anyway, but I'd be interested to know if there are any other pain points. Any issues with VPNs, if you're using them?

[meddlepal]

I haven’t tried a VPN yet, but I have heard of some possible quirks due to how the networking is handled between Windows and Linux in HyperV

Edit: Im switching from Fedora to a WSL setup for work in the next week. Ill report on issues I encounter in that migration. I suspect VPN will come up because one of the key reasons im switching off Fedora to Windows+WSL is due to corporate VPN requirements.

[running101]

This is the fix for vpn and wsl2 been running this for 6 months no issues. https://github.com/sakai135/wsl-vpnkit

[600frogs]

That'd be super great if you could let me know how it goes, I'm tempted to make the same jump. Thanks!

[meddlepal]

I'll reply to this comment when I do know