potiuk commented on issue #17132: URL: https://github.com/apache/airflow/issues/17132#issuecomment-884315771
Not really. All the packages are there: ``` docker run -it apache/airflow:2.1.2 bash airflow@af2bf98c9084:/opt/airflow$ pip | grep celery airflow@af2bf98c9084:/opt/airflow$ pipdeptree | grep celery bash: pipdeptree: command not found airflow@af2bf98c9084:/opt/airflow$ pip freeze | grep celery apache-airflow-providers-celery==2.0.0 celery==4.4.7 airflow@af2bf98c9084:/opt/airflow$ pip freeze | grep redis apache-airflow-providers-redis==2.0.0 google-cloud-redis==2.1.1 redis==3.5.3 airflow@af2bf98c9084:/opt/airflow$ pip freeze | grep psycopg2 psycopg2-binary==2.9.1 ``` The `lipq-dev` dependency should not be there. Airflow production image is highly optimized for runtime (for size) and it does not contain any of the -dev dependencies (also it does not contain `build essentials`. Those are only needed /added in the "build" segment during the image build and not installed in the "final" image where only runtime dependencies are added. That makes the image half the size it would be if all dev dependencies and build essentials were added. If you want to add your own custom dependencies you can build your own image following instructions in https://airflow.apache.org/docs/docker-stack/build.html - if you need `build essentials` and `-dev` dependencies you should go "custom image" route rather than "extend the image" one. Also I recommend to take a look at my talk where I explain how and why it is done: https://www.youtube.com/watch?v=wDr3Y7q2XoI Note, that in production image all the packages are installed in ${HOME}/.local (i.e. with the --user flag) so that you can easier extend the image without changing the user to root. Maybe that is the root cause of you thinking that the packages are not installed. -- 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]
