Hi Daniel, Are you able to get breeze working with WSL1? I have only been able to get docker and decent performance to the point where it's useable with WSL2. If Breeze works on both WSL1 and WSL2 it makes sense to specify this in the guide and split the instructions for the preferred choice.
For sure there are pros and cons between WSL1 and WSL2, almost a shame they're not just named differently as Microsoft plans to support both for now. I'm currently testing this environment using VS Code as my editor and manager of VCS, it runs on the Windows side but understands WSL2 directories so I am currently trialing this by keeping all the code in Linux directories not in Windows directories. Assuming WSL 2 becomes popular it seems likely that more dev tools will support this way of working. I had a quick test of pycharm by pointing it to the automatic WSL2 network share but it seems that it doesn't support all pycharm features yet. Damian -----Original Message----- From: Daniel Standish <dpstand...@gmail.com> Sent: Thursday, May 28, 2020 12:10 To: dev@airflow.apache.org Subject: Re: Airflow Dev on Windows using WSL2 I too was looking forward to trying WSL 2 because we have some windows users. One thing to keep in mind with WSL 2 is that it does not like to share files with windows. Here is a doc on the differences: https://docs.microsoft.com/en-us/windows/wsl/compare-versions And a note specifically on when WSL 1 is better: https://docs.microsoft.com/en-us/windows/wsl/compare-versions#exceptions-for-using-wsl-1-rather-than-wsl-2 WSL 1 actually works *ok* too. But if you want to use a gui git like sourcetree (or even do your VCS from pycharm), you kinda want your files on windows host. And if you want to use windows host, my sense is WSL 1 is going to remain the better option. They are talking about enabling running gui apps in wsl 2, down the road. And this would change things because your IDE and any gui git tools could live in WSL 2, and therefore so could your code. On Thu, May 28, 2020 at 7:37 AM Jarek Potiuk <jarek.pot...@polidea.com> wrote: > Wonderful! Thank you. We already have some description of using dev > env in WSL > https://github.com/apache/airflow/blob/master/BREEZE.rst#docker-in-wsl > -> > So maybe that's a good chance to review it and make some PR with > clarifications there :)? > > J. > > On Thu, May 28, 2020 at 4:32 PM Shaw, Damian P. < > damian.sha...@credit-suisse.com> wrote: > > > Hi all, > > > > I posted this earlier on Slack but I thought I'd also include it to > > the mailing list. > > > > Windows 10 2004 Stable just got released and it supports WSL2 > > meaning no need to use a preview ring anymore, and the latest > > version of Docker Desktop now supports Windows Home with WSL2 so no > > need to shell out $100 for Windows Pro anymore! > > > > I just did the following without any problem: > > > > 1. Got WSL2 working with Ubuntu: > > https://docs.microsoft.com/en-us/windows/wsl/install-win10 > > > > 2. Installed Docker Desktop (only non-default options WSL 2 > > backend): > https://docs.docker.com/docker-for-windows/install-windows-home > > > > 3. Git Cloned Apache Airflow in WSL2 Ubuntu (cd to ~ so it clones > > in Linux directory not Windows directory) > > > > 4. Ran ./breeze > > > > 5. Ran pytest > > > > Performance is significantly better than my previous attempts to run > > breeze under a virtualbox VM. > > > > Hope this helps, > > Damian > > > > > > > ====================================================================== > ========= > > > > Please access the attached hyperlink for an important electronic > > communications disclaimer: > > http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html > > > ====================================================================== > ========= > > > > > > > -- > > Jarek Potiuk > Polidea <https://www.polidea.com/> | Principal Software Engineer > > M: +48 660 796 129 <+48660796129> > [image: Polidea] <https://www.polidea.com/> > =============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ===============================================================================
