potiuk commented on issue #21723: URL: https://github.com/apache/airflow/issues/21723#issuecomment-1053528769
> Thank you for the clarification! My use case is using breeze to test the dag locally. Our production environment is on k8s and uses the production image. So I was trying to reproduce the same environment locally for test. It will be convenient to load production docker image via breeze, with the file system mounted, for local development. This is not really convenient/easy and you will not get what you want, because prod image of Airlfow has different way of installing sources. Sources in CI are just mounted in /opt/airflow. But Production image "airflow" is installed from packages (separately airflow packages amd separately provider package) - so mounting sources to prod image is not a good idea, because it contains both providers, and airlfow sources from main - where in the production image sources of airlfow are diffferent than sources of providers (they might come from completely different commits) I guess you do not want to mount "airlfow" sources, but your own sources, and in order to do that it is FAR easier to use plain docker commands rather than breeze: ``` docker run -it -v <your_sources>:/your_sources apache/airflow:2.2.4-python3.7 bash ``` ^^ this will mount your sources to `/your_sources` in the image. No need to get Breeze involved. -- 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]
