bitnami/flink

Verified Publisher

By VMware

Updated 3 days ago

Bitnami container image for Apache Flink

Image
Data Science
Internet of Things
Machine Learning & AI

100K+

Bitnami package for Apache Flink

What is Apache Flink?

Apache Flink is a framework and distributed processing engine for stateful computations over unbounded and bounded data streams.

Overview of Apache Flink

Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.

TL;DR

docker run --name flink bitnami/flink:latest

Why use Bitnami Images?

  • Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
  • With Bitnami images the latest bug fixes and features are available as soon as possible.
  • Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
  • All our images are based on minideb -a minimalist Debian based container image that gives you a small base container image and the familiarity of a leading Linux distribution- or scratch -an explicitly empty image-.
  • All Bitnami images available in Docker Hub are signed with Notation. Check this post to know how to verify the integrity of the images.
  • Bitnami container images are released on a regular basis with the latest distribution packages available.

Looking to use Apache Flink in production? Try VMware Tanzu Application Catalog, the commercial edition of the Bitnami catalog.

Only latest stable branch maintained in the free Bitnami catalog

Starting December 10th 2024, only the latest stable branch of any container will receive updates in the free Bitnami catalog. To access up-to-date releases for all upstream-supported branches, consider upgrading to Bitnami Premium. Previous versions already released will not be deleted. They are still available to pull from DockerHub.

Please check the Bitnami Premium page in our partner Arrow Electronics for more information.

Supported tags and respective Dockerfile links

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.

You can see the equivalence between the different tags by taking a look at the tags-info.yaml file present in the branch folder, i.e bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml.

Subscribe to project updates by watching the bitnami/containers GitHub repo.

Get this image

The recommended way to get the Bitnami flink Docker Image is to pull the prebuilt image from the Docker Hub Registry.

docker pull bitnami/flink:latest

To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.

docker pull bitnami/flink:[TAG]

If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the docker build command. Remember to replace the APP, VERSION and OPERATING-SYSTEM path placeholders in the example command below with the correct values.

git clone https://github.com/bitnami/containers.git
cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .

Why use a non-root container?

Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers in our docs.

Configuration

Environment variables

Customizable environment variables

NameDescriptionDefault Value
FLINK_MODEFlink default mode.jobmanager
FLINK_CFG_REST_PORTThe port that the client connects to.8081
FLINK_TASK_MANAGER_NUMBER_OF_TASK_SLOTSNumber of task slots for taskmanager.$(grep -c ^processor /proc/cpuinfo)
FLINK_PROPERTIESList of Flink cluster configuration options separated by new line, the same way as in the flink-conf.nil

Read-only environment variables

NameDescriptionValue
FLINK_BASE_DIRFlink installation directory.${BITNAMI_ROOT_DIR}/flink
FLINK_BIN_DIRFlink installation directory.${FLINK_BASE_DIR}/bin
FLINK_WORK_DIRFlink installation directory.${FLINK_BASE_DIR}
FLINK_LOG_DIRFlink log directory.${FLINK_BASE_DIR}/log
FLINK_CONF_DIRFlink configuration directory.${FLINK_BASE_DIR}/conf
FLINK_DEFAULT_CONF_DIRFlink configuration directory.${FLINK_BASE_DIR}/conf.default
FLINK_CONF_FILEFlink configuration file name.config.yaml
FLINK_CONF_FILE_PATHFlink configuration file path.${FLINK_CONF_DIR}/${FLINK_CONF_FILE}
FLINK_VOLUME_DIRFlink directory for mounted configuration files.${BITNAMI_VOLUME_DIR}/flink
FLINK_DATA_TO_PERSISTFiles to persist relative to the Flink installation directory. To provide multiple values, separate them with a whitespace.conf plugins
FLINK_DAEMON_USERFlink daemon system user.flink
FLINK_DAEMON_GROUPFlink daemon system group.flink
Running commands

To run commands inside this container you can use docker run. The default endpoint runs a Flink JobManager instance (jobmanager mode), while you can use the environment variable FLINK_MODE for run the image in a different mode:

Also, you can use the help Flink Mode in order to obtain an updated list of modes to run of different components instances

docker run --rm -e FLINK_MODE=help --name flink bitnami/flink:latest
$ Usage: FLINK_MODE=(jobmanager|standalone-job|taskmanager|history-server)

  By default, the Apache Flink Packaged by Bitnami  image will run in jobmanager mode.
  Also, by default, Apache Flink Packaged by Bitnami image adopts jemalloc as default memory allocator. This behavior can be disabled by setting the 'DISABLE_JEMALLOC' environment variable to 'true'.

Check the official Apache Flink documentation for more information.

Using docker-compose.yaml

Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated Bitnami Helm chart.

If you detect any issue in the docker-compose.yaml file, feel free to report it or contribute with a fix by following our Contributing Guidelines.

Contributing

We'd love for you to contribute to this container. You can request new features by creating an issue or submitting a pull request with your contribution.

Issues

If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to fill the issue template.

License

Copyright © 2025 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Docker Pull Command

docker pull bitnami/flink
Bitnami