You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I read here and there that's not possible (the reverse is possible as far as I know), but after upgrade to WSL2 1.1.0 and 1.1.2 I'm getting strange errors (bind: address in use on WSL2 process) that seem to show there is some form of "port sharing/forwarding" (not sure of appropriate naming) between Windows host and WSL2, so connecting to say localhost:8888 in a WSL2 process would connect to some server process listening on port 8888 on Windows.
Is my understanding correct or should I report an issue ?
Thanks
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I read here and there that's not possible (the reverse is possible as far as I know), but after upgrade to WSL2 1.1.0 and 1.1.2 I'm getting strange errors (bind: address in use on WSL2 process) that seem to show there is some form of "port sharing/forwarding" (not sure of appropriate naming) between Windows host and WSL2, so connecting to say localhost:8888 in a WSL2 process would connect to some server process listening on port 8888 on Windows.
Is my understanding correct or should I report an issue ?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions