[FLINK-12546] Base Docker images on `library/flink`

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.8.0
• Fix Version/s: 1.11.0
• Component/s: flink-docker
• Labels: usability
• Assignee: Unassigned
• Reporter: Konstantin Knauf
• Created: 17/May/19 13:11
• Updated: 15/Apr/20 15:17
• Resolved: 15/Apr/20 15:17

Description

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)

Issue Links

• is duplicated by: FLINK-15671 Provide one place for Docker Images with all supported cluster modes
• is related to: FLINK-17160 FLIP-111: Docker image unification
• relates to: FLINK-12375 flink-container job jar does not have read permissions
• relates to: FLINK-12416 Docker build script fails on symlink creation ln -s
• relates to: FLINK-10140 Log files are not available via web UI in containerized environment
• relates to: FLINK-15671 Provide one place for Docker Images with all supported cluster modes