flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ismaël Mejía (JIRA) <j...@apache.org>
Subject [jira] [Commented] (FLINK-3026) Publish the flink docker container to the docker registry
Date Thu, 09 Mar 2017 14:36:38 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903128#comment-15903128
] 

Ismaël Mejía commented on FLINK-3026:
-------------------------------------

I wonder still how could we address the issue of community awareness, I have thought about
two options:

1. We guarantee that the image in the apache/flink repo is always equivalent to the latest
version supported in the docker-flink repo (like this the community is aware and can continue
to improve it), so the maintenance of 'latest' will continue in apache.
2. We just remove everything from the docker contrib folder and mention somewhere in the main
README that the docker image is maintained in the docker-flink repo.

I am obviously pro 1, What do you think ?

> Publish the flink docker container to the docker registry
> ---------------------------------------------------------
>
>                 Key: FLINK-3026
>                 URL: https://issues.apache.org/jira/browse/FLINK-3026
>             Project: Flink
>          Issue Type: Task
>          Components: Build System, Docker
>            Reporter: Omer Katz
>            Assignee: Patrick Lucas
>              Labels: Deployment, Docker
>
> There's a dockerfile that can be used to build a docker container already in the repository.
It'd be awesome to just be able to pull it instead of building it ourselves.
> The dockerfile can be found at https://github.com/apache/flink/tree/master/flink-contrib/docker-flink
> It also doesn't point to the latest version of Flink which I fixed in https://github.com/apache/flink/pull/1366



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message