potiuk commented on issue #26274:
URL: https://github.com/apache/airflow/issues/26274#issuecomment-1242153733

   I think running Airlfow in WSL2 in production is not something we should 
recommend, There are multiple implications and problems (ranging from 
filesystem, networking issuess down to running Airflow in unattended way on 
Windows server, and making Airlfow to run in "Production" as opposed for 
"Development of Airflow" shoudl not happen (and adding this info to 
Installation" page implies running it in production. 
   
   I woudl be totally against any entry that suggest you can install Airlfow in 
WSL2 that would suggest that this is a setup people can "expect to work" and 
"get support from the community" about. If you have experience about runing 
Airlfow in production on WSL2 you could write Blog post about it and make a 
link from the "Ecosystem" page - but that would be maximum that you should do.
   
   We already have documentation about running Airflow in WSL2 for "Airflow 
Development" - i.e. contributing to Airlfow in our Github pages - to run 
Dockerized Breeze development environment in WSL2 
https://github.com/apache/airflow/blob/main/BREEZE.rst#docker-in-wsl-2  . One 
thing that is likely missing (and where you could contribute to is to add 
chapter about it in local virtuelenv case: 
https://github.com/apache/airflow/blob/main/LOCAL_VIRTUALENV.rst - there we 
have a generic venv case but likely adding WSL2 there and some specific things 
like filesystem use etc. might be useful.
   
   However - what  we should really focus on is to make Airlfow run on Windows 
natively. We are not far from that - with the completion of 
https://github.com/apache/airflow/projects/13 (Rewrite Breeze to Python), 
merging https://github.com/apache/airflow/pull/26105 (git clone on Windows) and 
successufl completion of https://github.com/apache/airflow/issues/12874 and 
https://github.com/apache/airflow/issues/10388 - we will be able to make first 
- development natively on Windows and later possibly even running Airflow in 
Production on Windows natively.
   
   This is far more important direction to follow and Rather than documenting 
how you can run Airlfow in WSL2 I'd rather see steps to implement Native 
Windows compatibility for Airflow.
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to