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 Mon, 06 Mar 2017 10:15:33 GMT

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

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

[~jgrier] I have been following the progress on FLINK-5634 and FLINK-5635 so I can retake
this one once they are merged (good work btw), so maybe this is a good moment to restart discussing.
Also since Max is not around at this moment maybe you are the appropriate person I should
discuss around this.

We have two alternatives:
1. Once is to ask infra and get the image in the apache account (users will do docker pull
apache/flink), this can have some annoyances since I have the impression we will depend on
infra for some things, but not sure 100%.
2. Try to have a docker official image. This one is nice because it has more visability (and
users will do docker pull flink).

I am really pro (2), 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: Ismaël Mejía
>              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

View raw message