You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Aizhamal Nurmamat kyzy (JIRA)" <ji...@apache.org> on 2019/05/18 02:40:01 UTC
[jira] [Updated] (AIRFLOW-3976) Create multi-stage dockerfile
[ https://issues.apache.org/jira/browse/AIRFLOW-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aizhamal Nurmamat kyzy updated AIRFLOW-3976:
--------------------------------------------
Labels: docker dockerfile (was: )
Component/s: (was: docker)
ci
I am moving these issues away from the docker component as part of the component refactoring[1]. I am moving to 'ci' component, but perhaps these are more appropriate as part of a 'build', or an 'installation' component, Thoughts [~Fokko][~ffinfo]?
The reason the docker component is being cleared out is that it invites dockeroperator issues, and issues like this. We'll use labels for docker-related issues, but let's separate operator-related issues from airflow dockerfile issues.
[1] https://docs.google.com/document/d/1gticSJ7LgD15XHgQhEP78-Ky38Er_NnMlarIvSQ8NYM/edit#
> Create multi-stage dockerfile
> -----------------------------
>
> Key: AIRFLOW-3976
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3976
> Project: Apache Airflow
> Issue Type: Improvement
> Components: ci
> Affects Versions: 1.10.2
> Reporter: Fokko Driesprong
> Priority: Major
> Labels: docker, dockerfile
> Fix For: 2.0.0
>
>
> The single stage dockerfile can become quite big when we include NPM in the build.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)