bitnami/spring-cloud-dataflow
Bitnami container image for Spring Cloud Data Flow
10M+
Spring Cloud Data Flow is a microservices-based toolkit for building streaming and batch data processing pipelines in Cloud Foundry and Kubernetes.
Overview of Spring Cloud Data Flow
docker run --name spring-cloud-dataflow bitnami/spring-cloud-dataflow:latest
Looking to use Spring Cloud Data Flow in production? Try VMware Tanzu Application Catalog, the commercial edition of the Bitnami catalog.
Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami Spring Cloud Data Flow Chart GitHub repository.
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.
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.
Dockerfile
linksLearn 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.
The recommended way to get the Bitnami spring-cloud-dataflow Docker Image is to pull the prebuilt image from the Docker Hub Registry.
docker pull bitnami/spring-cloud-dataflow: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/spring-cloud-dataflow:[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 .
Customizable environment variables
Name | Description | Default Value |
---|---|---|
SERVER_PORT | Custom port number to use for the SPRING CLOUD DATAFLOW Server service. | nil |
SPRING_CLOUD_CONFIG_ENABLED | Whether to load config using Spring Cloud Config Servie. | false |
SPRING_CLOUD_KUBERNETES_SECRETS_ENABLE_API | Whether to load config using Kubernetes API. | false |
SPRING_CLOUD_KUBERNETES_CONFIG_NAME | Name of the ConfigMap that contains the configuration. | nil |
SPRING_CLOUD_KUBERNETES_SECRETS_PATHS | Paths where the secrets are going to be mount. | nil |
SPRING_CLOUD_DATAFLOW_FEATURES_STREAMS_ENABLED | Whether enable stream feature in dataflow. It need SPRING_CLOUD_SKIPPER_CLIENT_SERVER_URI | false |
SPRING_CLOUD_DATAFLOW_FEATURES_TASKS_ENABLED | Whether enable tasks feature in dataflow. It need SPRING_CLOUD_SKIPPER_CLIENT_SERVER_URI | false |
SPRING_CLOUD_DATAFLOW_FEATURES_SCHEDULES_ENABLED | Whether enable schedules feature in dataflow. It need SPRING_CLOUD_SKIPPER_CLIENT_SERVER_URI | false |
SPRING_CLOUD_SKIPPER_CLIENT_SERVER_URI | Skipper server URI | nil |
SPRING_CLOUD_DATAFLOW_TASK_COMPOSEDTASKRUNNER_URI | Workaround for https://github.com/spring-cloud/spring-cloud-dataflow/issues/5072 | maven://org.springframework.cloud:spring-cloud-dataflow-composed-task-runner:${APP_VERSION:-} |
JAVA_OPTS | JVM options | nil |
JAVA_TOOL_OPTIONS | Java tool options. | nil |
Read-only environment variables
Name | Description | Value |
---|---|---|
SPRING_CLOUD_DATAFLOW_BASE_DIR | Base path for SPRING CLOUD DATAFLOW files. | ${BITNAMI_ROOT_DIR}/spring-cloud-dataflow |
SPRING_CLOUD_DATAFLOW_VOLUME_DIR | SPRING CLOUD DATAFLOW directory for persisted files. | ${BITNAMI_VOLUME_DIR}/spring-cloud-dataflow |
SPRING_CLOUD_DATAFLOW_CONF_DIR | SPRING CLOUD DATAFLOW configuration directory. | ${SPRING_CLOUD_DATAFLOW_BASE_DIR}/conf |
SPRING_CLOUD_DATAFLOW_CONF_FILE | Main SPRING CLOUD DATAFLOW configuration file. | ${SPRING_CLOUD_DATAFLOW_CONF_DIR}/application.yml |
SPRING_CLOUD_DATAFLOW_M2_DIR | SPRING CLOUD DATAFLOW maven root dir. | /.m2 |
SPRING_CLOUD_DATAFLOW_DAEMON_USER | Users that will execute the SPRING CLOUD DATAFLOW Server process. | dataflow |
SPRING_CLOUD_DATAFLOW_DAEMON_GROUP | Group that will execute the SPRING CLOUD DATAFLOW Server process. | dataflow |
Configuring database
A relational database is used to store stream and task definitions as well as the state of executed tasks. Spring Cloud Data Flow provides schemas for H2, MySQL, Oracle, PostgreSQL, Db2, and SQL Server. Use the following environment to configure the connection.
Configuring additional features
Spring Cloud Data Flow Server offers specific set of features that can be enabled/disabled when launching.
In the same way, you might need to customize the JVM. Use the JAVA_OPTS
environment variable for this purpose.
Configuring stream platform
In order to deploy streams using data flow you will require Spring Cloud Skipper and one of the following messaging platforms. Please add the following environment variable to point to a different skipper endpoint.
Using RabbitMQ
Using Kafka
Consult the spring-cloud-dataflow Reference Documentation to find the completed list of documentation.
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.
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.
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.
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.