potiuk commented on issue #26274: URL: https://github.com/apache/airflow/issues/26274#issuecomment-1243463144
> I’m not sure there’s much to add, really. After you spin up WSL2, you’re essentially in Linux, and can simply follow the “normal” deployment guides. Actually - there are quite a few caveats actually that has been nicely captured in the BREEZE docs (but due to us getting much closer to running airflow on Windows natively (and because we are - I think - never going to support Airflow for production, we should not make it "official" way of running airflow other than for local development : > # WSL 2 Filesystem Performance : > Accessing the host Windows filesystem incurs a performance penalty, it is therefore recommended to do development on the Linux filesystem. E.g. Run cd ~ and create a development folder in your Linux distro home and git pull the Airflow repo there. > * WSL 2 Docker mount errors: > Another reason to use Linux filesystem, is that sometimes - depending on the length of your path, you might get strange errors when you try start Breeze, such as caused: mount through procfd: not a directory: unknown:. Therefore checking out Airflow in Windows-mounted Filesystem is strongly discouraged. > * WSL 2 Docker volume remount errors: > If you're experiencing errors such as ERROR: for docker-compose_airflow_run Cannot create container for service airflow: not a directory when starting Breeze after the first time or an error like docker: Error response from daemon: not a directory. See 'docker run --help'. when running the pre-commit tests, you may need to consider [installing Docker directly in WSL 2](https://dev.to/bowmanjd/install-docker-on-windows-wsl-without-docker-desktop-34m9) instead of using Docker Desktop for Windows. > * WSL 2 Memory Usage : > WSL 2 can consume a lot of memory under the process name "Vmmem". To reclaim the memory after development you can: > On the Linux distro clear cached memory: sudo sysctl -w vm.drop_caches=3 > If no longer using Docker you can quit Docker Desktop (right click system try icon and select "Quit Docker Desktop") > If no longer using WSL you can shut it down on the Windows Host with the following command: wsl --shutdown > * Developing in WSL 2: > You can use all the standard Linux command line utilities to develop on WSL 2. Further VS Code supports developing in Windows but remotely executing in WSL. If VS Code is installed on the Windows host system then in the WSL Linux Distro you can run code . in the root directory of you Airflow repo to launch VS Code. -- 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]
