NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #1170 by repository stars
Latest stable
v0.3.5
Last release 4 years ago
no release in 18 months
Ships unpredictably
gaps range from 2 weeks to 2.5 years
Nearly every release is documented
notes for 9 of 9 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
13 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
From an elevated / Administrator console ```
v0.3.5 Changes
To upgrade:
From an elevated / Administrator console
> .\wsl2host.exe stop
> .\wsl2host.exe remove
> .\wsl2host.exe install
A more robust implementation of detecting the IP address using /proc (fix for #17)
v0.3.4 Changes
v0.3.3 Changes
To upgrade:
From an elevated / Administrator console
> .\wsl2host.exe stop
> .\wsl2host.exe remove
> .\wsl2host.exe install
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Introduce distro agnostic approach to getting WSL IP using /proc/net/fib_trie
v0.3.3 Changes
To upgrade:
From an elevated / Administrator console
> .\wsl2host.exe stop
> .\wsl2host.exe remove
> .\wsl2host.exe install
Fix error logic around getting IP from WSL2 VM
v0.3.1 Changes
Specifying aliases
As of v0.3 you can no specify aliases that point to your WSL2 VM IP. Having some.client.local, may be useful in your development workflow.
To do this, create the file ~/.wsl2hosts in your default WSL2 distro. Host names are space separated:
some.client.local my-app.local wsl.local
To upgrade:
From an elevated / Administrator console
> .\wsl2host.exe stop
> .\wsl2host.exe remove
> .\wsl2host.exe install
As of v0.3 you can no specify aliases that point to your WSL2 VM IP. Having some.client.local, may be useful in your development workflow.
v0.3.1 Changes
f.Sync() call #9Specifying aliases
As of v0.3 you can no specify aliases that point to your WSL2 VM IP. Having some.client.local, may be useful in your development workflow.
To do this, create the file ~/.wsl2hosts in your default WSL2 distro. Host names are space separated:
some.client.local my-app.local wsl.local
To upgrade:
From an elevated / Administrator console
> .\wsl2host.exe stop
> .\wsl2host.exe remove
> .\wsl2host.exe install
As of v0.3 you can no specify aliases that point to your WSL2 VM IP. Having some.client.local, may be useful in your development workflow.
v0.3.0 Changes
Specifying aliases
As of v0.3 you can no specify aliases that point to your WSL2 VM IP. Having some.client.local, may be useful in your development workflow.
To do this, create the file ~/.wsl2hosts in your default WSL2 distro. Host names are space separated:
some.client.local my-app.local wsl.local
To upgrade:
From an elevated / Administrator console
> .\wsl2host.exe stop
> .\wsl2host.exe remove
> .\wsl2host.exe install
Make remove more robust in cleaning up service and eventlog source (clean remove)
v0.2.2 changes
remove more robust in cleaning up service and eventlog source (clean remove)NOTE: Upgrading Windows Insider will remove the service, but not cleanly. To reinstall after upgrading, first make sure you've downloaded the latest version of wsl2host, then run remove before install
To upgrade:
From an elevated / Administrator console
> .\wsl2host.exe stop
> .\wsl2host.exe remove
> .\wsl2host.exe install
Only update hosts file if change detected
v0.2.1 changes
Complete re-write
<distro-hostname>.wsl. Distro names are normalized to hostnames, i.e. Ubuntu-18.04 becomes ubuntu1804.wsl.<distro-hostname>.wslwindows.local, if this was important let me know.To upgrade:
From an elevated / Administrator console
> .\wsl2host.exe stop
> .\wsl2host.exe remove
> .\wsl2host.exe install
Changes to use .wsl. Distro names are normalized to hostnames, i.e. Ubuntu-18.04 becomes ubuntu1804.wsl.
Complete re-write
<distro-hostname>.wsl. Distro names are normalized to hostnames, i.e. Ubuntu-18.04 becomes ubuntu1804.wsl.<distro-hostname>.wslwindows.local, if this was important let me know.To upgrade:
From an elevated / Administrator console
> .\wsl2host.exe stop
> .\wsl2host.exe remove
> .\wsl2host.exe install
Support multiple IP addresses from `hostname -I`
Support multiple IP addresses from hostname -I
If docker is running multiple IP addresses are returned by hostname -I,
we take the first one now.
Also if we update the IP address and it's shorter (in characters) than the last IP address we have a corrupt wsl line, we now add a couple empty lines to try and mitigate that.
To install and run, download a binary from the releases tab. Place it somewhere like your Documents/ folder.
To install and run, download a binary from the releases tab. Place it somewhere like your Documents/ folder.
Open an elevated/administrator command prompt:
> .\go-wsl2-host.exe install
Windows Username: <username-you-use-to-login-to-windows>
Windows Password: <password-for-this-user>
Nothing published for this version
One column per quarter.