potiuk commented on issue #41853:
URL: https://github.com/apache/airflow/issues/41853#issuecomment-2317919336
You have not mentioned it but my guess is that you are dynamically
installing packages and after this dynamic installation - ikely your image
actually runs lower version of Airlfow.
The revision is in the alembic table so the migration worked - but the
airflow command you run uses a downgraded version of airflow after your
dynamic `pip install` command.
Please take a look on what version of the image you are using and whether
your customization / extending the image has some problems. For example when
you are installing dynamically new packages - the `pip install` command might
automatically downgrade airflow. It solely depends on packages you install and
resolution of pip which might decide that downgrading airflow fulfills other
dependencies better.
That's why in the offiical installation description of upgrade scenarios,
you will find that you always have to specify
`apache-airflow=${AIRFLOW_VERSION}`
https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-pypi.html#installation-and-upgrade-scenarios
- so that `pip` won't downgrade airflow.
This is one of the reasons why we always discouraged installing packages
dynamically when your image starts - because for example airlfow version might
change - but also other packages might and recommend users to build their own
image - this way they can be sure what version of packages they have there.
With dynamic package
--
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]
