-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
[AIRFLOW-6662] Switch to --init docker flag for signal propagation #7278
[AIRFLOW-6662] Switch to --init docker flag for signal propagation #7278
Conversation
Codecov Report
@@ Coverage Diff @@
## master #7278 +/- ##
==========================================
+ Coverage 85.2% 85.46% +0.26%
==========================================
Files 840 851 +11
Lines 40336 40403 +67
==========================================
+ Hits 34367 34531 +164
+ Misses 5969 5872 -97
Continue to review full report at Codecov.
|
We are now using native --init flag of docker run and init: parameter of docker compose to pass signals and reap child processes
9343807
to
ff50596
Compare
@ashb @nuclearpinguin @mik-laj @feluelle -> I fixed it all by --init flag. |
@ashb @mik-laj @nuclearpinguin -> Seems the init flag is good now. I tested it and it all works fine including killing the running local builds with Ctrl-C. That was the biggest problem before dumb-init introduction and it works perfectly now. |
…ation (apache#7278)" This reverts commit d1bf343.
* Revert "[AIRFLOW-6662] Switch to --init docker flag for signal propagation (#7278)" This reverts commit d1bf343. * [AIRFLOW-6662] return back the dumb-init - installed by apt We had stability problems with tests with --init flag so we are going back to it
* Revert "[AIRFLOW-6662] Switch to --init docker flag for signal propagation (#7278)" This reverts commit d1bf343. * [AIRFLOW-6662] return back the dumb-init - installed by apt We had stability problems with tests with --init flag so we are going back to it (cherry picked from commit 945b988)
* Revert "[AIRFLOW-6662] Switch to --init docker flag for signal propagation (#7278)" This reverts commit d1bf343. * [AIRFLOW-6662] return back the dumb-init - installed by apt We had stability problems with tests with --init flag so we are going back to it (cherry picked from commit 945b988)
…pache#7278) We are now using native --init flag of docker run and init: parameter of docker compose to pass signals and reap child processes
* Revert "[AIRFLOW-6662] Switch to --init docker flag for signal propagation (apache#7278)" This reverts commit d1bf343. * [AIRFLOW-6662] return back the dumb-init - installed by apt We had stability problems with tests with --init flag so we are going back to it
…pache#7278) We are now using native --init flag of docker run and init: parameter of docker compose to pass signals and reap child processes (cherry picked from commit d1bf343) (cherry picked from commit 85cde61)
* Revert "[AIRFLOW-6662] Switch to --init docker flag for signal propagation (apache#7278)" This reverts commit d1bf343. * [AIRFLOW-6662] return back the dumb-init - installed by apt We had stability problems with tests with --init flag so we are going back to it (cherry picked from commit 945b988) (cherry picked from commit 3ca84ec)
We are now using native --init flag of docker run and init: parameter
of docker compose to pass signals and reap child processes
Issue link: AIRFLOW-6662
Make sure to mark the boxes below before creating PR: [x]
[AIRFLOW-NNNN]
. AIRFLOW-NNNN = JIRA ID** For document-only changes commit message can start with
[AIRFLOW-XXXX]
.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.