You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by po...@apache.org on 2022/06/02 11:33:28 UTC
[airflow] branch main updated: Add note about Docker volume remount issues in WSL 2 (#24094)
This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 382c636193 Add note about Docker volume remount issues in WSL 2 (#24094)
382c636193 is described below
commit 382c63619342b28c5f208bb7ca14b54033accbe0
Author: Paul Williams <pd...@udel.edu>
AuthorDate: Thu Jun 2 07:33:12 2022 -0400
Add note about Docker volume remount issues in WSL 2 (#24094)
---
BREEZE.rst | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/BREEZE.rst b/BREEZE.rst
index 8f5a6e1053..b80db9c453 100644
--- a/BREEZE.rst
+++ b/BREEZE.rst
@@ -127,10 +127,18 @@ Docker in WSL 2
- **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 us
+ 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: