airflow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hitesh Shah <hit...@apache.org>
Subject Re: Docker file for Airflow master
Date Thu, 07 Feb 2019 19:11:17 GMT
[Moving the conversation to dev@, BCC'ed private@]

Or we can follow the same approach followed by other ASF projects that have
been certified as official images:
https://hub.docker.com/search?q=apache&type=image&image_filter=official

thanks
Hitesh

On Thu, Feb 7, 2019 at 10:56 AM Hitesh Shah <hitesh@apache.org> wrote:

And +1 to not pushing to dockerhub except for releases that have been
> reviewed.
>
> thanks
> Hitesh
>
> On Thu, Feb 7, 2019 at 9:45 AM Tao Feng <fengtao04@gmail.com> wrote:
>
>> Hey Fokko,
>>
>> I am not very familiar with these processes, but just want to make sure
>> Airflow follows Apache's guideline. If you have concern or questions, I
>> would suggest you chime in that email thread pointed by Arthur and clarify
>> with those experts(like Justin).
>>
>> Thanks,
>> -Tao
>>
>> On Thu, Feb 7, 2019 at 9:30 AM Arthur Wiedmer <arthur.wiedmer@gmail.com>
>> wrote:
>>
>>> Hi Fokko,
>>>
>>> I think Justin's observation here are the key:
>>>
>>> https://mail-archives.apache.org/mod_mbox/incubator-general/201902.mbox/%3CDDC5A74B-1537-4022-B7D6-D4EF8669C675%40classsoftware.com%3E
>>>
>>> Convenience Binary packages can be shipped, but only of released
>>> software. As such only our releases are "released", all othe commits on
>>> master are not. The main issue seems to be the confusion that Apache might
>>> endorse the Docker images. If we release master baked images, it needs to
>>> come with a warning label and disclaimer, that this is not an apache
>>> release etc...
>>>
>>> Best,
>>> Arthur
>>>
>>> On Thu, Feb 7, 2019 at 12:12 AM Driesprong, Fokko <fokko@driesprong.frl>
>>> wrote:
>>>
>>>> Hi Tao,
>>>>
>>>> The link to the mailing-list ends up in the general overview. The idea
>>>> is that we have both the releases with their specific tag (which isn't set
>>>> up yet), and have a master tag which reflects the latest master. This makes
>>>> it easier to test the Kubernetes stuff since we can just run the latest
>>>> master. Of course, I would not recommend this for anything in production.
>>>>
>>>> Can you point to the docs where it disallows pushing source to
>>>> Dockerhub?
>>>>
>>>> Cheers, Fokko
>>>>
>>>>
>>>> Op do 7 feb. 2019 om 08:14 schreef Tao Feng <fengtao04@gmail.com>:
>>>>
>>>>> Hi,
>>>>>
>>>>> Since this pr(https://github.com/apache/airflow/pull/4483) is merged,
>>>>> it seems that every commit will get pushed to DockerHub as the master
tag.
>>>>> And one discussion in the general mailing list(
>>>>> https://mail-archives.apache.org/mod_mbox/incubator-general/201902.mbox/browser)
>>>>> caught my eye.  It seems that Apache disallows source pushing to Dockerhub
>>>>> if it is not an official apache release.
>>>>>
>>>>> What do you think? Should we remove the Dockerfile in Airflow repo(
>>>>> https://github.com/apache/airflow/blob/master/Dockerfile) or at least
>>>>> disable the pushing step?
>>>>>
>>>>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message