Skip to content

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Jun 1, 2025

When we are building PROD image we use pip rather than uv, however we should be able to use uv to do it. Recently we had a bug that broke it - by using --group dev unconditionally - even if we used airflow packages to build airflow.

So far we always run the PROD build with pip that's why it worked fine, but once fix building with both uv and pip we can build the images with uv by default and run a pip build separately in extra checks.

Fixes: #50134


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

@boring-cyborg boring-cyborg bot added area:dev-tools area:production-image Production image improvements and fixes labels Jun 1, 2025
@potiuk potiuk force-pushed the fix-building-prod-images-with-uv branch from 7ef91ca to 9edaac6 Compare June 1, 2025 17:21
@potiuk potiuk marked this pull request as ready for review June 1, 2025 18:33
@potiuk potiuk requested review from ashb and gopidesupavan as code owners June 1, 2025 18:33
@potiuk potiuk added the canary When set on PR running from apache repo - behave as canary run label Jun 1, 2025
When we are building PROD image we use `pip` rather than `uv`, however
we should be able to use `uv` to do it. Recently we had a bug that
broke it - by using `--group dev` unconditionally - even if
we used airflow packages to build airflow.

So far we always run the PROD build with `pip` that's why it worked
fine, but once fix building with both uv and pip we can build the
images with uv by default and run a pip build separately in extra
checks.

Fixes: apache#50134
@potiuk potiuk force-pushed the fix-building-prod-images-with-uv branch from 9edaac6 to 9bb5664 Compare June 1, 2025 18:33
@potiuk potiuk added this to the Airflow 3.0.2 milestone Jun 1, 2025
@potiuk potiuk added the backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch label Jun 1, 2025
@potiuk potiuk merged commit 92a4d60 into apache:main Jun 2, 2025
102 checks passed
@potiuk potiuk deleted the fix-building-prod-images-with-uv branch June 2, 2025 08:45
github-actions bot pushed a commit that referenced this pull request Jun 2, 2025
When we are building PROD image we use `pip` rather than `uv`, however
we should be able to use `uv` to do it. Recently we had a bug that
broke it - by using `--group dev` unconditionally - even if
we used airflow packages to build airflow.

So far we always run the PROD build with `pip` that's why it worked
fine, but once fix building with both uv and pip we can build the
images with uv by default and run a pip build separately in extra
checks.
(cherry picked from commit 92a4d60)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Fixes: #50134
@github-actions
Copy link

github-actions bot commented Jun 2, 2025

Backport successfully created: v3-0-test

Status Branch Result
v3-0-test PR Link

potiuk added a commit that referenced this pull request Jun 2, 2025
When we are building PROD image we use `pip` rather than `uv`, however
we should be able to use `uv` to do it. Recently we had a bug that
broke it - by using `--group dev` unconditionally - even if
we used airflow packages to build airflow.

So far we always run the PROD build with `pip` that's why it worked
fine, but once fix building with both uv and pip we can build the
images with uv by default and run a pip build separately in extra
checks.
(cherry picked from commit 92a4d60)


Fixes: #50134

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
kaxil pushed a commit that referenced this pull request Jun 3, 2025
When we are building PROD image we use `pip` rather than `uv`, however
we should be able to use `uv` to do it. Recently we had a bug that
broke it - by using `--group dev` unconditionally - even if
we used airflow packages to build airflow.

So far we always run the PROD build with `pip` that's why it worked
fine, but once fix building with both uv and pip we can build the
images with uv by default and run a pip build separately in extra
checks.
(cherry picked from commit 92a4d60)


Fixes: #50134

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
sanederchik pushed a commit to sanederchik/airflow that referenced this pull request Jun 7, 2025
When we are building PROD image we use `pip` rather than `uv`, however
we should be able to use `uv` to do it. Recently we had a bug that
broke it - by using `--group dev` unconditionally - even if
we used airflow packages to build airflow.

So far we always run the PROD build with `pip` that's why it worked
fine, but once fix building with both uv and pip we can build the
images with uv by default and run a pip build separately in extra
checks.

Fixes: apache#50134
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools area:production-image Production image improvements and fixes backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch canary When set on PR running from apache repo - behave as canary run

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Dockerfile 3.0.0 does not work with uv enabled

4 participants