potiuk commented on issue #44771: URL: https://github.com/apache/airflow/issues/44771#issuecomment-2537219979
I think you need to provide a bit more information. Windows/WSL2 is not really a target platform for airflow runtime for "production" and we do not run any tests with it. But maybe - if you can do some analysis and provide more information we can attempt to help you in your problem. You can try to gather some more logs and information - i.e. gather more detailed logs from example tasks - to see which processes have been created - if you look and trace it in the logs and send us the info, maybe we can help you to figure out some workarounds. Track what processes are being created. Also if you are using `run_as_user` - feature, there might be a problem with WSL2 or your impersonation user settings. There few parameters you can try - https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#execute-tasks-new-python-interpreter might be something worth trying. Converting to a discussion, as Windows/WSL2 is not a target runtime platform - but there might be a discussion coming out of it. -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
