-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WSL1 #493
Comments
Thanks for the investigation. We will support WSL1 if we can, but we may just elect to require WSL2, I have updated our docs for now. Is there any reason we really should support WSL1? As that will sway our choices. |
Some points that speak for supporting WSL1:
|
This is a pretty good reason lol. K we gotta support WSL1. Sounds like WSL2 is not mature or recommended yet. |
I don't think this is still true: https://learn.microsoft.com/en-us/windows/wsl/install
That said, it's easy to have a WSL 1 install, either on an older Windows, predating the new default, or by "downgrading". Notably: https://learn.microsoft.com/en-us/windows/wsl/compare-versions#comparing-features It looks like WSL1 neither has a full Linux kernel, nor the full syscall availability. That might mean it needs to be built as its own binary variant. It looks like even |
k well if WSL2 is the current default then that needs supporting firstly. Do we work with WSL2? I have a windows machine so I should check this out myself. |
I've had no problems with tea and WSL2 so far, been using for a month or so. |
Yes, we've have no noteworthy bug reports for WSL2, given its reasonable similarity to a dockerized environment. |
Closing in lieu of #607 |
Re-installed my computer and was put back to WSL1. This caused some problems (#490, #491) which were solved by upgrading to WSL2. I believe WSL1 is the default version.
It seems tea does not play nice with WSL1.
The text was updated successfully, but these errors were encountered: