Web UI from version 3.0.0 is loaded when using apache/airflow:2.9.0 image via Docker Compose

[herbertstos]

Apache Airflow version

Other Airflow 2 version (please specify below)

If "Other Airflow 2 version" selected, which one?

No response

What happened?

I'm using Docker Compose with the official apache/airflow:2.9.0 image. However, the Web UI that is loaded appears to be from Airflow 3.0.0 — the layout and design match the new interface. I’ve confirmed the image tag is 2.9.0, and Docker shows it pulling and using the correct image, but the UI still behaves like version 3.0.0.

What you think should happen instead?

No response

How to reproduce

Set apache/airflow:2.9.0 in docker-compose.yml.

Run docker-compose up.

Access the Web UI and observe the version and layout.

Operating System

windows 11 - wls ubuntu lastest

Versions of Apache Airflow Providers

Expected Behavior:
The UI should match Airflow 2.9.0, not 3.0.0.

Deployment

Official Apache Airflow Helm Chart

Deployment details

The deployment was done following the official Airflow documentation.
https://airflow.apache.org/docs/apache-airflow/2.9.0/howto/docker-compose/index.html

Anything else?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg[bot]]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

[potiuk]

Almost certainly you have not followed the docs and tried to add some dependencies dynamically with pip that caused airflow to be updated (for example by using _PIP_ADDITIONAL_REQUIREMENTS or some scripts to run pip installation). Which we very strongly tell people not to do because they can accidentally upgrade airflow if they do not pin it:

This is straight explained in our documentation https://airflow.apache.org/docs/apache-airflow/2.9.0/howto/docker-compose/index.html#using-custom-images

It is the best practice to install apache-airflow in the same version as the one that comes from the original image. This way you can be sure that pip will not try to downgrade or upgrade apache airflow while installing other requirements, which might happen in case you try to add a dependency that conflicts with the version of apache-airflow that you are using.

If you did that mistake - you should do it "properly" and build your custom image in this case -> see detailed instructions under the links I posted above.

[potiuk]

BTW. I followed the exact instructions described in the docs and as I expected I got 2.9.0 UI.

The deployment was done following the official Airflow documentation.
https://airflow.apache.org/docs/apache-airflow/2.9.0/howto/docker-compose/index.html

So the above is wrong - you MUST have done something else. You have not mentioned how you deviated from the "quick-start" - so my guess about adding dependencies is just a guess.

My recommendation is that if you do deviate from literally every single step described in the docs, first thing to do is to show how your case is customized and modified vs. the exact process described in the docs. That helps to loose less time trying to guess what you did.

[potiuk]

Ideally - if you will still neead help. post a log of things you've done, marking any deviations vs. standard thing visibly.

[potiuk]

Converted it to a discussion.