flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Zagrebin (Jira)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-12546) Base Docker images on `library/flink`
Date Wed, 15 Apr 2020 15:18:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-12546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Andrey Zagrebin closed FLINK-12546.
    Release Note: Superseded by FLIP-111 (FLINK-17160)
      Resolution: Won't Fix

> 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
>              Labels: usability
>             Fix For: 1.11.0
> 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

View raw message