-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Use mariadb by default when build final prod image
#36716
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
I guess we should also mention that in the docker-stack release notes (changing 2.8.0 -> 2.8.1) ? |
|
Yeah I think also need to mention that if someone build custom image from 2.8.0 branch then should specify Let me find better place for that |
|
Merged. Re-building images here https://github.com/apache/airflow/actions/runs/7479928533/job/20358188520 |
|
OK. Images refreshed - they failed verification, but the verification failure was "fab" provider missing (which is expected). |
We forget to change default value for
INSTALL_MYSQL_CLIENT_TYPEargument tomariadb.So we build packages by MariaDB libraries, however finally install mysql.
This only affects
X86_64images because for ARM we always use MariaDB libraries regardless of this build argumentrelated: #36715 (this only fix further images, but not 2.8)
^ 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.rstor{issue_number}.significant.rst, in newsfragments.