potiuk edited a comment on issue #20168: URL: https://github.com/apache/airflow/issues/20168#issuecomment-991209264
NEVER use `extraPipPackages` or equivalent in production. We warn against trying to do similar thing for similar case with images https://airflow.apache.org/docs/docker-stack/entrypoint.html#installing-additional-requirements - and we had a number of discussions and warned @thesuperzapper that those kind of cases like yours will be happening. That's perfect example of why you should not do it. (@thesuperzapper - I hope you will be able to help diagnose the observed behaviour and help @jensgrnb). Instead you should build your own image: https://airflow.apache.org/docs/docker-stack/build.html and use that image for all your components. There ar plenty of examples, including how to upgrade provider, how to update packages etc. in our docs. Then you can stay with Matthew's chart, or switch to the officially supported package by the Airflow Community - https://airflow.apache.org/docs/helm-chart/stable/index.html (where we would never, ever, advice our users to dyamically install packages in their image) - we don't really force you to use our chart. Feel free to open an issue in https://github.com/airflow-helm/charts where it belongs and possibly get Matthew's help on fixing the problem, but this is not really airflow bug. -- 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]
