potiuk commented on a change in pull request #16170:
URL: https://github.com/apache/airflow/pull/16170#discussion_r642134765
##########
File path: docs/docker-stack/entrypoint.rst
##########
@@ -185,66 +259,24 @@ database and creating an ``admin/admin`` Admin user with
the following command:
The commands above perform initialization of the SQLite database, create admin
user with admin password
and Admin role. They also forward local port ``8080`` to the webserver port
and finally start the webserver.
-Waits for celery broker connection
-----------------------------------
-
-In case Postgres or MySQL DB is used, and one of the ``scheduler``,
``celery``, ``worker``, or ``flower``
-commands are used the entrypoint will wait until the celery broker DB
connection is available.
-
-The script detects backend type depending on the URL schema and assigns
default port numbers if not specified
-in the URL. Then it loops until connection to the host/port specified can be
established
-It tries :envvar:`CONNECTION_CHECK_MAX_COUNT` times and sleeps
:envvar:`CONNECTION_CHECK_SLEEP_TIME` between checks.
-To disable check, set ``CONNECTION_CHECK_MAX_COUNT=0``.
-
-Supported schemes:
-
-* ``amqp(s)://`` (rabbitmq) - default port 5672
-* ``redis://`` - default port 6379
-* ``postgres://`` - default port 5432
-* ``mysql://`` - default port 3306
-
-Waiting for connection involves checking if a matching port is open.
-The host information is derived from the variables
:envvar:`AIRFLOW__CELERY__BROKER_URL` and
-:envvar:`AIRFLOW__CELERY__BROKER_URL_CMD`. If
:envvar:`AIRFLOW__CELERY__BROKER_URL_CMD` variable
-is passed to the container, it is evaluated as a command to execute and result
of this evaluation is used
-as :envvar:`AIRFLOW__CELERY__BROKER_URL`. The
:envvar:`AIRFLOW__CELERY__BROKER_URL_CMD` variable
-takes precedence over the :envvar:`AIRFLOW__CELERY__BROKER_URL` variable.
-
-.. _entrypoint:commands:
-
-Executing commands
-------------------
-
-If first argument equals to "bash" - you are dropped to a bash shell or you
can executes bash command
-if you specify extra arguments. For example:
-
-.. code-block:: bash
-
- docker run -it apache/airflow:2.1.0-python3.6 bash -c "ls -la"
- total 16
- drwxr-xr-x 4 airflow root 4096 Jun 5 18:12 .
- drwxr-xr-x 1 root root 4096 Jun 5 18:12 ..
- drwxr-xr-x 2 airflow root 4096 Jun 5 18:12 dags
- drwxr-xr-x 2 airflow root 4096 Jun 5 18:12 logs
-
-If first argument is equal to ``python`` - you are dropped in python shell or
python commands are executed if
-you pass extra parameters. For example:
-
-.. code-block:: bash
+Installing additional requirements
+..................................
- > docker run -it apache/airflow:2.1.0-python3.6 python -c "print('test')"
- test
+Installing additional requirements can be done by specifying
``_PIP_ADDITIONAL_REQUIREMENTS`` variable.
+The variable should contain a list of requirements that should be installed
additionally when entering
+the containers. Note that this option slows down starting of Airflow as every
time any container starts
+it must install new packages. Therefore this option should only be used for
testing. When testing is
+finished, yoy should create your custom image with dependencies baked in.
Review comment:
```suggestion
finished, you should create your custom image with dependencies baked in.
```
--
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.
For queries about this service, please contact Infrastructure at:
[email protected]
