-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
Proper version is displayed when running prod image via Breeze #8229
Proper version is displayed when running prod image via Breeze #8229
Conversation
Note that this is only applicable to production image. --install-airflow-version in CI works slightly differently. In production image it builds a new image. In CI image it installs airflow version in the original "2.0" image (uninstalls airflow 2.0 first). This is much faster and OK for testing. For production image - we really want to build the image in an optimal way so the image is rebuild using the version of airflow provided via --install-airflow-version flag. |
Codecov Report
@@ Coverage Diff @@
## master #8229 +/- ##
==========================================
- Coverage 88.35% 87.92% -0.44%
==========================================
Files 936 936
Lines 45305 46065 +760
==========================================
+ Hits 40030 40503 +473
- Misses 5275 5562 +287
Continue to review full report at Codecov.
|
Hey @feluelle - can you double check if this works :) ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works. Thanks @potiuk :)
@potiuk That is really weird ->
EDIT: being on git branch #8228 (and rebased on latest master) |
it is :). Looking at it |
Can you try the same with |
with When I remove all |
YEah. I think the reason was source mapping to inside the container. I left comment in #8228 to remove all the /opt/airflow mounts. This might be super-misleading if we leave them. |
Luckily I have not yet merged it so you can still fix it :) |
Will do - thanks for helping :) |
Make sure to mark the boxes below before creating PR: [x]
In case of fundamental code change, 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 UPDATING.md.
Read the Pull Request Guidelines for more information.