Comment by chazeon | Hacker News Reader

Comment by chazeon | Hacker News Reader

Not being able to access WSL from within an SSH session due to

  "not possible to access wsl from session 0 (which is where the Windows OpenSSH server run)" [1,2]

is now a deal breaker for me to upgrade to whatever they called 1.0.0 version or released over Windows Store.

The old version (non-Store version) used to work, and now the upgraded / non-Preview version doesn't. I don't know how they dare remove that preview tag.

[1]: https://github.com/microsoft/WSL/issues/9059

[2]: https://devblogs.microsoft.com/commandline/a-preview-of-wsl-...

This is a great example to keep in mind against the high praise WSL receives— not because it's particularly dire, but because it's representative of how surprising (and basically intractable) WSL issues generally are. The product is chock full of bugs like this which will only impact a small subset of users, but which are showstoppers for that subset. (Some of them can be worked around, but good God are they a PITA.)

They tend to be issues that 'seem' advanced, but the missing functionality is usually something that the vast majorities of developers who have run a Linux desktop for development would take for granted as a possibility.

You're you saying if I ssh into windows and am dumped into powershell, I'm unable to type wsl to drop into linux?

Yes, that is the case when you upgrade to the current version.

Bummer, but at least it's described as a "known issue" and the fix appears to be in progress.

This hack might help some: https://www.hanselman.com/blog/how-to-ssh-into-wsl2-on-windo...

Reply on news.ycombinator.com