You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Christian Barra (JIRA)" <ji...@apache.org> on 2018/06/22 21:27:00 UTC
[jira] [Updated] (AIRFLOW-2665) No BASH will cause the dag to fail
[ https://issues.apache.org/jira/browse/AIRFLOW-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Barra updated AIRFLOW-2665:
-------------------------------------
Summary: No BASH will cause the dag to fail (was: No BASH will cause a the dag to fail)
> No BASH will cause the dag to fail
> ----------------------------------
>
> Key: AIRFLOW-2665
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2665
> Project: Apache Airflow
> Issue Type: Bug
> Reporter: Christian Barra
> Priority: Major
>
> If you are a running airflow in a system where bash is not available the dags will fail, with no logs inside the UI (you have to scroll trough the local logs).
> How to replicate this? just use an alpine based image:
> ```
> [2018-06-22 21:05:20,659] \{jobs.py:1386} INFO - Processing DAG_1
> [2018-06-22 21:05:20,667] \{local_executor.py:43} INFO - LocalWorker running airflow run DAG_1 stackoverflow 2018-06-22T21:05:19.384402 --local -sd /usr/local/airflow/dags/my_dag.py
> /bin/sh: exec: line 1: bash: not found
> [2018-06-22 21:05:20,671] \{local_executor.py:50} ERROR - Failed to execute task Command 'exec bash -c 'airflow run DAG_1 my_task 2018-06-22T21:05:19.384402 --local -sd /usr/local/airflow/dags/my_dag.py'' returned non-zero exit status 127..
> /bin/sh: exec: line 1: bash: not found
> ```
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)