-
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
Expose Airflow Webserver Port in Production Docker Image #8228
Expose Airflow Webserver Port in Production Docker Image #8228
Conversation
@potiuk Is it correct that we should map the port like I did in every backend compose file? |
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.
Few comments :)
74f861a
to
1cffa75
Compare
1cffa75
to
3ecca89
Compare
Ready for re-review @potiuk |
Looks Great! |
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.
I also had an issue with volumes being mounted
|
3ecca89
to
0ad4ac4
Compare
Yes, without it - it works. |
But the |
Indeed. I think we should move ports to "base.yaml". I can't think of any reason why it would be harm. |
But then you won't be able to test prod image locally while having airflow ci running, because both are using the same port EDIT:
|
I think there are more reasons why you cannot run both prod/ci in parallel - they use the same docker-compose configuration and they are both named "airflow" so I would not worry about that. I think you should always stop the CI Breeze before starting Prod one. We might add some better diagnosis/explanation of the case rather than "port listening" error. |
Yes that is true. It is not only that - both are using the same database if for example both (by default) have backend mysql or postgres. (which is configured in the compose file :D) |
Should I add docs regarding that in this PR? Just a note about what you said not using both at the same time? |
Absolutely :) |
0ad4ac4
to
116279a
Compare
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.
Just one comment for the example - it's not valid right now as you might use different constraint requirements than the ones matching the version you want to build.
Codecov Report
@@ Coverage Diff @@
## master #8228 +/- ##
==========================================
- Coverage 88.43% 88.42% -0.01%
==========================================
Files 940 940
Lines 45353 45355 +2
==========================================
- Hits 40108 40106 -2
- Misses 5245 5249 +4
Continue to review full report at Codecov.
|
116279a
to
b4ecb42
Compare
@potiuk can you check again, please? |
Perfect! Thanks @feluelle ! Let's wait for Travis and I am super happy to merge it :) |
Are we good to go @potiuk ? :) |
Go! Thanks @feluelle ! |
The production docker image currently does not expose a port which is needed for Airflow's webserver to be accessible from the host. This PR exposes a port and the breeze script will pass the port configured in breeze env.
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.