potiuk commented on issue #37785: URL: https://github.com/apache/airflow/issues/37785#issuecomment-1971849235
Found a way around it. For Airflow 2.9, uv should be fully supported - https://github.com/apache/airflow/pull/37796 regardless if uv flag will be supported or not by `uv`. @yehoshuadimarsky -> can you please test if that solves your problem? The way how to test it: - take the Dockerfile from that PR - build customized image following the ```bash export AIRFLOW_VERSION=2.82 export DOCKER_BUILDKIT=1 docker build . \ --build-arg PYTHON_BASE_IMAGE="python:3.8-slim-bookworm" \ --build-arg AIRFLOW_VERSION="${AIRFLOW_VERSION}" \ --tag "my-tag:0.0.1" ``` This should be built by `pip` - but when you get the image, you can extend it - latest `uv` version should be already in and should work without the need of adding any flags. You can also make another test: ```bash export AIRFLOW_VERSION=2.82 export DOCKER_BUILDKIT=1 docker build . \ --build-arg PYTHON_BASE_IMAGE="python:3.8-slim-bookworm" \ --build-arg AIRFLOW_VERSION="${AIRFLOW_VERSION}" \ --build-arg AIRFLOW_USE_UV="true" \ --tag "my-tag:0.0.1" ``` Should use `uv` to build the docker image. That one (according to my tests) should be 50%-60% faster to build from scratch comparing to the `pip` one. We do not want to enable it by default, but it should be fully usable and working. Can you please test and give feedback @yehoshuadimarsky ? -- 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]
