[
https://issues.apache.org/jira/browse/FLINK-12546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847710#comment-16847710
]
Yun Tang commented on FLINK-12546:
----------------------------------
[~knaufk] Thanks for your interpretation, and I would agree with you that
{{from-archive}} option seems not so useful in this view. The only thing I use
{{from-archive}} is when I try to fix FLINK-12416. I found if I always use
{{from-release}} to verify the {{Dockerfile}} change, it has to download the
archive Flink package from release site every time which really consume much
time for me. For users, if he has to verify its user jar many times with
{{from-release}} option, downloading the release archive would take too much
time. I think we should add a cache future.
However, I just wonder if we base our image on
[https://github.com/docker-flink/docker-flink], how we handle the Flink images
before Flink-1.7. As you can see, only Flink-1.7 and Flink-1.8 images would be
built. Moreover, if {{Flink}} relays on {{docker-flink}} to build docker image
while {{docker-flink}} would also depend on {{Flink}} release, do you think
this is a bit weird? How about involve {{docker-flink}} within {{Flink}}?
> Base Docker images on `library/flink`
> -------------------------------------
>
> Key: FLINK-12546
> URL: https://issues.apache.org/jira/browse/FLINK-12546
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Docker
> Affects Versions: 1.8.0
> Reporter: Konstantin Knauf
> Priority: Major
>
> Currently, Flink users turn to two different places when looking for
> "official" community Docker images.
> * https://github.com/docker-flink/docker-flink (Flink community maintained,
> no official Apache releases) or https://hub.docker.com/_/flink/
> * The tooling and Dockerfile in the {{flink-container}} component
> While users should turn to the Flink images on Docker Hub in general, the
> {{flink-container}} component is used by many users, because it contains some
> tooling to build images for the {{StandaloneJobClusterEntrypoint}}. Overall,
> this causes confusion for users and the community needs to maintain two
> Dockerfiles, which build Flink images FROM alpine or debian.
> Therefore, I propose to change the tooling ({{build.sh}}) in
> {{flink-container}} to have only two options:
> a) {{from-release}}, which uses `library/flink` as base image and basically
> only adds the user jar. (<--- for Flink users)
> b) {{from-local-dist}}, which also uses `library/flink` as base image but
> replaces the flink-dist by the local flink-dist ( <--- for Flink developer)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
