GitHub user potiuk added a comment to the discussion: Building Dockerfile with Changes
Generally the Dockerfle (and airflow) is not designed or supposed to work "out-of-the-box" for any changes you want to build locally -the dockerfile is used as part of "airflow" development workflow but you should follow contribution workflow and contributing docs https://github.com/apache/airflow/tree/main/contributing-docs if you want to build and run alrlow locally. There is a "CI" image that is built from sources (and contains a lot more things that are supposed to be used for Airflow development). There several other steps like asset compilation and then either preparing airflow `uv` workspace with multiple packages/distributions (Airflow consists of ~ 100 of python distributions overall). The Dockerfile (PROD)- by default installs airflow from released packages not from sources - even in CI of ours we build the packages locally first and then we use them to test PROD images - you can see more details on ways how you could build the image from packages https://airflow.apache.org/docs/docker-stack/build.html If you want to do it yourself - you can probably reverse engineer the way how our CI builds and creates the images for testing - but the image was never meant to be used by users to install their own local modifications in an easy way. GitHub link: https://github.com/apache/airflow/discussions/51660#discussioncomment-13451142 ---- This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
