ashb commented on code in PR #55662:
URL: https://github.com/apache/airflow/pull/55662#discussion_r2348933145
##########
airflow-core/docs/howto/docker-compose/index.rst:
##########
@@ -153,6 +153,23 @@ If you want to initialize ``airflow.cfg`` with default
values before launching t
docker compose run airflow-cli airflow config list
This will seed ``airflow.cfg`` with default values in ``config`` folder.
+On systems with SELinux/AppArmor, you may run into permission issues. If this
happens, edit your `docker-compose.yaml` file by added the suffix `:z` to all
volumes:
+
+.. code-block:: text
+
+ volumes:
+ - ${AIRFLOW_PROJ_DIR:-.}/dags:/opt/airflow/dags:z
+ - ${AIRFLOW_PROJ_DIR:-.}/logs:/opt/airflow/logs:z
+ - ${AIRFLOW_PROJ_DIR:-.}/config:/opt/airflow/config:z
+ - ${AIRFLOW_PROJ_DIR:-.}/plugins:/opt/airflow/plugins:z
+
+If, after this change, you are still experiencing permission issues when
creating the `airflow.cfg` file, you can apply a very permissive setting to the
`config` folder:
Review Comment:
```suggestion
If, after this change, you are still experiencing permission issues when
creating the ``airflow.cfg`` file, you can apply a very permissive setting to
the `config` folder:
```
##########
airflow-core/docs/howto/docker-compose/index.rst:
##########
@@ -153,6 +153,23 @@ If you want to initialize ``airflow.cfg`` with default
values before launching t
docker compose run airflow-cli airflow config list
This will seed ``airflow.cfg`` with default values in ``config`` folder.
+On systems with SELinux/AppArmor, you may run into permission issues. If this
happens, edit your `docker-compose.yaml` file by added the suffix `:z` to all
volumes:
+
+.. code-block:: text
+
+ volumes:
+ - ${AIRFLOW_PROJ_DIR:-.}/dags:/opt/airflow/dags:z
+ - ${AIRFLOW_PROJ_DIR:-.}/logs:/opt/airflow/logs:z
+ - ${AIRFLOW_PROJ_DIR:-.}/config:/opt/airflow/config:z
+ - ${AIRFLOW_PROJ_DIR:-.}/plugins:/opt/airflow/plugins:z
+
+If, after this change, you are still experiencing permission issues when
creating the `airflow.cfg` file, you can apply a very permissive setting to the
`config` folder:
+
+.. code-block:: bash
+
+ sudo chmod -R 777 ./config
+
+Note that the above is a _work around_ that should never be used in production.
Review Comment:
`_` is markdown. In rst we use `*` for em and `**` for bold.
```suggestion
Note that the above is a *work around* that should never be used in
production.
```
##########
airflow-core/docs/howto/docker-compose/index.rst:
##########
@@ -153,6 +153,23 @@ If you want to initialize ``airflow.cfg`` with default
values before launching t
docker compose run airflow-cli airflow config list
This will seed ``airflow.cfg`` with default values in ``config`` folder.
+On systems with SELinux/AppArmor, you may run into permission issues. If this
happens, edit your `docker-compose.yaml` file by added the suffix `:z` to all
volumes:
Review Comment:
```suggestion
On systems with SELinux/AppArmor, you may run into permission issues. If
this happens, edit your ``docker-compose.yaml`` file by added the suffix ``:z``
to all volumes:
```
##########
airflow-core/docs/howto/docker-compose/index.rst:
##########
@@ -153,6 +153,23 @@ If you want to initialize ``airflow.cfg`` with default
values before launching t
docker compose run airflow-cli airflow config list
This will seed ``airflow.cfg`` with default values in ``config`` folder.
+On systems with SELinux/AppArmor, you may run into permission issues. If this
happens, edit your `docker-compose.yaml` file by added the suffix `:z` to all
volumes:
+
+.. code-block:: text
Review Comment:
```suggestion
.. code-block:: yaml
```
--
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]
