![]() Successfully installed more-itertools-8.2.0 packaging-20.3 pluggy-0.13.1 py-1.8.1 pyparsing-2.4.7 pytest-5.4.1 wcwidth-0.1. since the issue is solved for you without making any additional changes in the docker-compose my guess would be scheduler somehow read the AIRFLOWCOREEXECUTOR as SequentialExecutor (default) and not the CeleryExecutor as you configured. WARNING: The scripts py.test and pytest are installed in '/usr/local/airflow/.local/bin' which is not on PATH.Ĭonsider adding this directory to PATH or, if you prefer to suppress this warning, use -no-warn-script-location. Installing collected packages: more-itertools, wcwidth, pyparsing, packaging, pluggy, py, pytest Requirement already satisfied: six in /usr/local/lib/python3.7/site-packages (from packaging->pytest->-r /requirements.txt (line 1)) (1.14.0)ĭownloading pyparsing-2.4.7-py2.p圓-none-any.whl (67 kB) Requirement already satisfied: zipp>=0.5 in /usr/local/lib/python3.7/site-packages (from importlib-metadata>=0.12 python_version pytest->-r /requirements.txt (line 1)) (2.2.0) Requirement already satisfied: attrs>=17.4.0 in /usr/local/lib/python3.7/site-packages (from pytest->-r /requirements.txt (line 1)) (19.3.0) Requirement already satisfied: importlib-metadata>=0.12 python_version -r /requirements.txt (line 1)) (1.5.0)ĭownloading 圓-none-any.whl (37 kB)ĭownloading pluggy-0.13.1-py2.p圓-none-any.whl (18 kB)ĭownloading py-1.8.1-py2.p圓-none-any.whl (83 kB) Which will force a docker-compose rebuild the image. I.e instead run: docker-compose -f docker-compose-dev.yml up -build -d. doneĭownloading pytest-5.4.1-p圓-none-any.whl (246 kB) In order to get docker-compose to include your changes to your requirements.txt you will need to pass the -build flag to docker-compose. Starting airflow-on-docker-compose_postgres_1. FROM python:3.8-slim COPY requirements.txt /tmp/requirements.txt RUN pip. Let's edit our first DAG: dags/dummy_dag.py Docker containers, and manage all these with Docker Compose. we share our dags/test/plugins directories with the host so we can just edit our code on our local machine and run all the tests in container.we will use postgres instance running as another docker container.we allow to pass custom environment variables straight from the dotenv file (best practice is not include it in the files).Test: "]Īs you can see we have several things there:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |