@Fokko my initial use was to: - create a container that was setup with environment variables (including some in the entrypoint.sh, as in https://github.com/puckel/docker-airflow) and no custom configuration. - generate the config file to persist it so that when executing commands in the container, airflow CLI would work without having to setup all the environment variables needed
The problem being that the CLI (and I suppose other daemons) needs some of the same environment variables than the running webserver. My current workaround is to run commands through `entrypoint.sh`, which sets up all the needed environment variables. This works as long as the entrypoint script is not making mutations to the filesystem. Maybe the original issue wasn't the correct way to tackle this problem though... I will leave that decision to the airflow team :) [ Full content available at: https://github.com/apache/incubator-airflow/pull/3867 ] This message was relayed via gitbox.apache.org for [email protected]
