[
https://issues.apache.org/jira/browse/AIRFLOW-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17028407#comment-17028407
]
ASF subversion and git services commented on AIRFLOW-6662:
----------------------------------------------------------
Commit 86f43eb0249fd96ca87be6c438cdb4c55b8dc142 in airflow's branch
refs/heads/v1-10-test from Jarek Potiuk
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=86f43eb ]
[AIRFLOW-6662] install dumb init (#7300)
* Revert "[AIRFLOW-6662] Switch to --init docker flag for signal propagation
(#7278)"
This reverts commit d1bf343ffec505270d4b2ee4b0e9fa5dbbedd891.
* [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 945b988cc255ba96ac2252a6084c2a662c935497)
> Switch to --init docker flag for signal propagation
> ---------------------------------------------------
>
> Key: AIRFLOW-6662
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6662
> Project: Apache Airflow
> Issue Type: Improvement
> Components: ci, tests
> Affects Versions: 2.0.0, 1.10.7
> Reporter: Jarek Potiuk
> Priority: Major
> Fix For: 1.10.8
>
>
> We are now using native --init flag of docker run and init: parameter of
> docker compose to pass signals and reap child processes
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
