[
https://issues.apache.org/jira/browse/FLINK-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903127#comment-15903127
]
Ismaël Mejía commented on FLINK-3026:
-------------------------------------
I suppose most projects do this to avoid having a plethora of repeated
dockerfiles where the only difference is the release version number, which
makes sense, also because this solves the evolution problem that we will have
now (with the start-foreground scripts that are coming in 1.3.0).
The only thing that is lost with this approach of having an external repo is
the community awareness about the docker images.
[~plucas] I like your plan, I would like to have FLINK-6003 merged first (I
think this one apart of adding the new non-alpine image it fixes important
issues like the resolution of the taskmanagers in the docker-compose file.
Afterwards just tell me the exact address of the repo and I will jump in to
prepare everything to put the official images in place,
> 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)
