public_git
/
bitnami-containers
mirror of https://github.com/bitnami/containers.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
bitnami-containers/bitnami/airflow
History
Bitnami Bot 42e97999e9
[bitnami/airflow] Release 3.1.1-debian-12-r0 (#87915) 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
 		2025-10-27 17:14:25 +01:00
..
2
…
3/debian-12 [bitnami/airflow] Release 3.1.1-debian-12-r0 (#87915) 2025-10-27 17:14:25 +01:00
README.md
…
docker-compose-ldap.yml
…
docker-compose.yml
…

README.md

Bitnami Secure Image for Apache Airflow

What is Apache Airflow?

Apache Airflow is a tool to express and execute workflows as directed acyclic graphs (DAGs). It includes utilities to schedule tasks, monitor task progress and handle task dependencies.

Overview of Apache Airflow 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 airflow bitnami/airflow:latest

Warning: This quick setup is only intended for development environments. You are encouraged to change the insecure default credentials and check out the available configuration options in the Environment Variables section for a more secure d eployment.

⚠️ Important Notice: Upcoming changes to the Bitnami Catalog

Beginning August 28th, 2025, Bitnami will evolve its public catalog to offer a curated set of hardened, security-focused images under the new Bitnami Secure Images initiative. As part of this transition:

  • Granting community users access for the first time to security-optimized versions of popular container images.
  • Bitnami will begin deprecating support for non-hardened, Debian-based software images in its free tier and will gradually remove non-latest tags from the public catalog. As a result, community users will have access to a reduced number of hardened images. These images are published only under the “latest” tag and are intended for development purposes
  • Starting August 28th, over two weeks, all existing container images, including older or versioned tags (e.g., 2.50.0, 10.6), will be migrated from the public catalog (docker.io/bitnami) to the “Bitnami Legacy” repository (docker.io/bitnamilegacy), where they will no longer receive updates.
  • For production workloads and long-term support, users are encouraged to adopt Bitnami Secure Images, which include hardened containers, smaller attack surfaces, CVE transparency (via VEX/KEV), SBOMs, and enterprise support.

These changes aim to improve the security posture of all Bitnami users by promoting best practices for software supply chain integrity and up-to-date deployments. For more details, visit the Bitnami Secure Images announcement.

Why use Bitnami Secure Images?

  • Bitnami Secure Images and Helm charts are built to make open source more secure and enterprise ready.
  • Triage security vulnerabilities faster, with transparency into CVE risks using industry standard Vulnerability Exploitability Exchange (VEX), KEV, and EPSS scores.
  • Our hardened images use a minimal OS (Photon Linux), which reduces the attack surface while maintaining extensibility through the use of an industry standard package format.
  • Stay more secure and compliant with continuously built images updated within hours of upstream patches.
  • 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.
  • Hardened images come with attestation signatures (Notation), SBOMs, virus scan reports and other metadata produced in an SLSA-3 compliant software factory.

Only a subset of BSI applications are available for free. Looking to access the entire catalog of applications as well as enterprise support? Try the commercial edition of Bitnami Secure Images today.

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.

Prerequisites

To run this application you need Docker Engine >= 1.10.0. Docker Compose is recommended with a version 1.6.0 or later.

How to use this image

Airflow requires access to a PostgreSQL database to store information. We will use our very own PostgreSQL image for the database requirements. Additionally, if you pretend to use the CeleryExecutor, you will also need a Redis(R) server.

Using the Docker Command Line

  1. Create a network

    docker network create airflow-tier

  2. Create a volume for PostgreSQL persistence and create a PostgreSQL container

    docker volume create --name postgresql_data
docker run -d --name postgresql \
  -e POSTGRESQL_USERNAME=bn_airflow \
  -e POSTGRESQL_PASSWORD=bitnami1 \
  -e POSTGRESQL_DATABASE=bitnami_airflow \
  --net airflow-tier \
  --volume postgresql_data:/bitnami/postgresql \
  bitnami/postgresql:latest

  3. Create a volume for Redis(R) persistence and create a Redis(R) container

    docker volume create --name redis_data
docker run -d --name redis \
  -e ALLOW_EMPTY_PASSWORD=yes \
  --net airflow-tier \
  --volume redis_data:/bitnami \
  bitnami/redis:latest

  4. Launch the Apache Airflow web container

    docker run -d --name airflow -p 8080:8080 \
  -e AIRFLOW_FERNET_KEY=46BKJoQYlPPOexq0OhDZnIlNepKFf87WFwLbfzqDDho= \
  -e AIRFLOW_SECRET_KEY=a25mQ1FHTUh3MnFRSk5KMEIyVVU2YmN0VGRyYTVXY08= \
  -e AIRFLOW_EXECUTOR=CeleryExecutor \
  -e AIRFLOW_DATABASE_NAME=bitnami_airflow \
  -e AIRFLOW_DATABASE_USERNAME=bn_airflow \
  -e AIRFLOW_DATABASE_PASSWORD=bitnami1 \
  -e AIRFLOW_LOAD_EXAMPLES=yes \
  -e AIRFLOW_PASSWORD=bitnami123 \
  -e AIRFLOW_USERNAME=user \
  -e AIRFLOW_EMAIL=user@example.com \
  --net airflow-tier \
  bitnami/airflow:latest

  5. Launch the Apache Airflow scheduler container

    docker run -d --name airflow-scheduler \
  -e AIRFLOW_COMPONENT_TYPE=scheduler \
  -e AIRFLOW_FERNET_KEY=46BKJoQYlPPOexq0OhDZnIlNepKFf87WFwLbfzqDDho= \
  -e AIRFLOW_SECRET_KEY=a25mQ1FHTUh3MnFRSk5KMEIyVVU2YmN0VGRyYTVXY08= \
  -e AIRFLOW_EXECUTOR=CeleryExecutor \
  -e AIRFLOW_DATABASE_NAME=bitnami_airflow \
  -e AIRFLOW_DATABASE_USERNAME=bn_airflow \
  -e AIRFLOW_DATABASE_PASSWORD=bitnami1 \
  -e AIRFLOW_LOAD_EXAMPLES=yes \
  -e AIRFLOW_WEBSERVER_HOST=airflow \
  --net airflow-tier \
  bitnami/airflow:latest

  6. Launch the Apache Airflow worker container

    docker run -d --name airflow-worker \
  -e AIRFLOW_COMPONENT_TYPE=worker \
  -e AIRFLOW_FERNET_KEY=46BKJoQYlPPOexq0OhDZnIlNepKFf87WFwLbfzqDDho= \
  -e AIRFLOW_SECRET_KEY=a25mQ1FHTUh3MnFRSk5KMEIyVVU2YmN0VGRyYTVXY08= \
  -e AIRFLOW_EXECUTOR=CeleryExecutor \
  -e AIRFLOW_DATABASE_NAME=bitnami_airflow \
  -e AIRFLOW_DATABASE_USERNAME=bn_airflow \
  -e AIRFLOW_DATABASE_PASSWORD=bitnami1 \
  -e AIRFLOW_WEBSERVER_HOST=airflow \
  --net airflow-tier \
  bitnami/airflow:latest

Access your application at http://your-ip:8080

Using docker-compose.yaml

curl -LO https://raw.githubusercontent.com/bitnami/containers/main/bitnami/airflow/docker-compose.yml
docker-compose up

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.

Persisting your application

The Bitnami Airflow container relies on the PostgreSQL database & Redis to persist the data. This means that Airflow does not persist anything. To avoid loss of data, you should mount volumes for persistence of PostgreSQL data and Redis(R) data

The above examples define docker volumes namely postgresql_data, and redis_data. The Airflow application state will persist as long as these volumes are not removed.

To avoid inadvertent removal of these volumes you can mount host directories as data volumes. Alternatively you can make use of volume plugins to host the volume data.

Mount host directories as data volumes with Docker Compose

The following docker-compose.yml template demonstrates the use of host directories as data volumes.

version: '2'
services:
  postgresql:
    image: bitnami/postgresql:latest
    environment:
      - POSTGRESQL_DATABASE=bitnami_airflow
      - POSTGRESQL_USERNAME=bn_airflow
      - POSTGRESQL_PASSWORD=bitnami1
    volumes:
      - /path/to/postgresql-persistence:/bitnami/postgresql
  redis:
    image: bitnami/redis:latest
    environment:
      - ALLOW_EMPTY_PASSWORD=yes
    volumes:
      - /path/to/redis-persistence:/bitnami
  airflow-worker:
    image: bitnami/airflow:latest
    environment:
      - AIRFLOW_COMPONENT_TYPE=worker
      - AIRFLOW_FERNET_KEY=46BKJoQYlPPOexq0OhDZnIlNepKFf87WFwLbfzqDDho=
      - AIRFLOW_SECRET_KEY=a25mQ1FHTUh3MnFRSk5KMEIyVVU2YmN0VGRyYTVXY08=
      - AIRFLOW_EXECUTOR=CeleryExecutor
      - AIRFLOW_DATABASE_NAME=bitnami_airflow
      - AIRFLOW_DATABASE_USERNAME=bn_airflow
      - AIRFLOW_DATABASE_PASSWORD=bitnami1
      - AIRFLOW_LOAD_EXAMPLES=yes
  airflow-scheduler:
    image: bitnami/airflow:latest
    environment:
      - AIRFLOW_COMPONENT_TYPE=scheduler
      - AIRFLOW_FERNET_KEY=46BKJoQYlPPOexq0OhDZnIlNepKFf87WFwLbfzqDDho=
      - AIRFLOW_SECRET_KEY=a25mQ1FHTUh3MnFRSk5KMEIyVVU2YmN0VGRyYTVXY08=
      - AIRFLOW_EXECUTOR=CeleryExecutor
      - AIRFLOW_DATABASE_NAME=bitnami_airflow
      - AIRFLOW_DATABASE_USERNAME=bn_airflow
      - AIRFLOW_DATABASE_PASSWORD=bitnami1
      - AIRFLOW_LOAD_EXAMPLES=yes
  airflow:
    image: bitnami/airflow:latest
    environment:
      - AIRFLOW_FERNET_KEY=46BKJoQYlPPOexq0OhDZnIlNepKFf87WFwLbfzqDDho=
      - AIRFLOW_SECRET_KEY=a25mQ1FHTUh3MnFRSk5KMEIyVVU2YmN0VGRyYTVXY08=
      - AIRFLOW_EXECUTOR=CeleryExecutor
      - AIRFLOW_DATABASE_NAME=bitnami_airflow
      - AIRFLOW_DATABASE_USERNAME=bn_airflow
      - AIRFLOW_DATABASE_PASSWORD=bitnami1
      - AIRFLOW_PASSWORD=bitnami123
      - AIRFLOW_USERNAME=user
      - AIRFLOW_EMAIL=user@example.com
    ports:
      - 8080:8080

Mount host directories as data volumes using the Docker command line

  1. Create a network (if it does not exist)

    docker network create airflow-tier

  2. Create the PostgreSQL container with host volumes

    docker run -d --name postgresql \
  -e POSTGRESQL_USERNAME=bn_airflow \
  -e POSTGRESQL_PASSWORD=bitnami1 \
  -e POSTGRESQL_DATABASE=bitnami_airflow \
  --net airflow-tier \
  --volume /path/to/postgresql-persistence:/bitnami \
  bitnami/postgresql:latest

  3. Create the Redis(R) container with host volumes

    docker run -d --name redis \
  -e ALLOW_EMPTY_PASSWORD=yes \
  --net airflow-tier \
  --volume /path/to/redis-persistence:/bitnami \
  bitnami/redis:latest

  4. Create the Airflow container

    docker run -d --name airflow -p 8080:8080 \
  -e AIRFLOW_FERNET_KEY=46BKJoQYlPPOexq0OhDZnIlNepKFf87WFwLbfzqDDho= \
  -e AIRFLOW_SECRET_KEY=a25mQ1FHTUh3MnFRSk5KMEIyVVU2YmN0VGRyYTVXY08= \
  -e AIRFLOW_EXECUTOR=CeleryExecutor \
  -e AIRFLOW_DATABASE_NAME=bitnami_airflow \
  -e AIRFLOW_DATABASE_USERNAME=bn_airflow \
  -e AIRFLOW_DATABASE_PASSWORD=bitnami1 \
  -e AIRFLOW_LOAD_EXAMPLES=yes \
  -e AIRFLOW_PASSWORD=bitnami123 \
  -e AIRFLOW_USERNAME=user \
  -e AIRFLOW_EMAIL=user@example.com \
  --net airflow-tier \
  bitnami/airflow:latest

  5. Create the Airflow Scheduler container

    docker run -d --name airflow-scheduler \
  -e AIRFLOW_COMPONENT_TYPE=scheduler \
  -e AIRFLOW_FERNET_KEY=46BKJoQYlPPOexq0OhDZnIlNepKFf87WFwLbfzqDDho= \
  -e AIRFLOW_SECRET_KEY=a25mQ1FHTUh3MnFRSk5KMEIyVVU2YmN0VGRyYTVXY08= \
  -e AIRFLOW_EXECUTOR=CeleryExecutor \
  -e AIRFLOW_DATABASE_NAME=bitnami_airflow \
  -e AIRFLOW_DATABASE_USERNAME=bn_airflow \
  -e AIRFLOW_DATABASE_PASSWORD=bitnami1 \
  -e AIRFLOW_LOAD_EXAMPLES=yes \
  -e AIRFLOW_WEBSERVER_HOST=airflow \
  --net airflow-tier \
  bitnami/airflow:latest

  6. Create the Airflow Worker container

    docker run -d --name airflow-worker \
  -e AIRFLOW_COMPONENT_TYPE=worker \
  -e AIRFLOW_FERNET_KEY=46BKJoQYlPPOexq0OhDZnIlNepKFf87WFwLbfzqDDho= \
  -e AIRFLOW_SECRET_KEY=a25mQ1FHTUh3MnFRSk5KMEIyVVU2YmN0VGRyYTVXY08= \
  -e AIRFLOW_EXECUTOR=CeleryExecutor \
  -e AIRFLOW_DATABASE_NAME=bitnami_airflow \
  -e AIRFLOW_DATABASE_USERNAME=bn_airflow \
  -e AIRFLOW_DATABASE_PASSWORD=bitnami1 \
  -e AIRFLOW_WEBSERVER_HOST=airflow \
  --net airflow-tier \
  bitnami/airflow:latest

Configuration

Load DAG files

Custom DAG files can be mounted to /opt/bitnami/airflow/dags.

Installing additional python modules

This container supports the installation of additional python modules at start-up time. In order to do that, you can mount a requirements.txt file with your specific needs under the path /bitnami/python/requirements.txt.

Environment variables

Customizable environment variables

Name Description Default Value
AIRFLOW_USERNAME Airflow username user
AIRFLOW_PASSWORD Airflow password bitnami
AIRFLOW_FIRSTNAME Airflow firstname Firstname
AIRFLOW_LASTNAME Airflow lastname Lastname
AIRFLOW_EMAIL Airflow email user@example.com
AIRFLOW_COMPONENT_TYPE Airflow component type. Allowed values: api-server, scheduler, dag-processor, triggerer, webserver (2.x versions only), worker. api-server
AIRFLOW_EXECUTOR Airflow executor. LocalExecutor
AIRFLOW_RAW_FERNET_KEY Airflow raw/unencoded Fernet key nil
AIRFLOW_FORCE_OVERWRITE_CONF_FILE Force the airflow.cfg config file generation. no
AIRFLOW_FERNET_KEY Airflow Fernet key nil
AIRFLOW_WEBSERVER_SECRET_KEY Airflow webserver secret key airflow-web-server-key
AIRFLOW_APISERVER_SECRET_KEY Airflow API secret key airflow-api-server-key
AIRFLOW_APISERVER_BASE_URL Airflow API server base URL. nil
AIRFLOW_APISERVER_HOST Airflow API server host 127.0.0.1
AIRFLOW_APISERVER_PORT_NUMBER Airflow API server port. 8080
AIRFLOW_LOAD_EXAMPLES To load example tasks into the application. yes
AIRFLOW_HOSTNAME_CALLABLE Method to obtain the hostname. nil
AIRFLOW_POOL_NAME Pool name. nil
AIRFLOW_POOL_SIZE Pool size, required with AIRFLOW_POOL_NAME. nil
AIRFLOW_POOL_DESC Pool description, required with AIRFLOW_POOL_NAME. nil
AIRFLOW_STANDALONE_DAG_PROCESSOR Enable running Dag Processor in standalone mode no
AIRFLOW_TRIGGERER_DEFAULT_CAPACITY How many triggers a single Triggerer can run at once. 1000
AIRFLOW_WORKER_QUEUE A queue for the worker to pull tasks from. nil
AIRFLOW_SKIP_DB_SETUP Skip db init / db migrate actions during the setup no
PYTHONPYCACHEPREFIX Configure Python .pyc files cache prefix /opt/bitnami/airflow/venv/tmp
AIRFLOW_DB_MIGRATE_TIMEOUT How much time to wait for database migrations 120
AIRFLOW_ENABLE_HTTPS Whether to enable HTTPS for Airflow by default. no
AIRFLOW_EXTERNAL_APISERVER_PORT_NUMBER External HTTP/HTTPS port for Airflow. 80
AIRFLOW_DATABASE_HOST Hostname for PostgreSQL server. postgresql
AIRFLOW_DATABASE_PORT_NUMBER Port used by PostgreSQL server. 5432
AIRFLOW_DATABASE_NAME Database name that Airflow will use to connect with the database. bitnami_airflow
AIRFLOW_DATABASE_USERNAME Database user that Airflow will use to connect with the database. bn_airflow
AIRFLOW_DATABASE_PASSWORD Database password that Airflow will use to connect with the database. nil
AIRFLOW_DATABASE_USE_SSL Set to yes if the database is using SSL. no
AIRFLOW_REDIS_USE_SSL Set to yes if Redis(R) uses SSL. no
REDIS_HOST Hostname for Redis(R) server. redis
REDIS_PORT_NUMBER Port used by Redis(R) server. 6379
REDIS_USER User that Airflow will use to connect with Redis(R). nil
REDIS_PASSWORD Password that Airflow will use to connect with Redis(R). nil
REDIS_DATABASE Name of the Redis(R) database. 1
AIRFLOW_LDAP_ENABLE Enable LDAP authentication. no
AIRFLOW_LDAP_URI LDAP server URI. nil
AIRFLOW_LDAP_SEARCH LDAP search base. nil
AIRFLOW_LDAP_UID_FIELD LDAP field used for uid. nil
AIRFLOW_LDAP_BIND_USER LDAP user name. nil
AIRFLOW_LDAP_BIND_PASSWORD LDAP user password. nil
AIRFLOW_LDAP_USER_REGISTRATION User self registration. True
AIRFLOW_LDAP_USER_REGISTRATION_ROLE Role name to be assign when a user registers himself. nil
AIRFLOW_LDAP_ROLES_MAPPING Mapping from LDAP DN to a list of Airflow roles. nil
AIRFLOW_LDAP_ROLES_SYNC_AT_LOGIN Replace ALL the user roles each login, or only on registration. True
AIRFLOW_LDAP_USE_TLS Use LDAP SSL. False
AIRFLOW_LDAP_ALLOW_SELF_SIGNED Allow self signed certicates in LDAP ssl. True
AIRFLOW_LDAP_TLS_CA_CERTIFICATE File that store the CA for LDAP ssl. nil

Read-only environment variables

Name Description Value
AIRFLOW_BASE_DIR Airflow home/installation directory. ${BITNAMI_ROOT_DIR}/airflow
AIRFLOW_BIN_DIR Airflow directory for binary executables. ${AIRFLOW_BASE_DIR}/venv/bin
AIRFLOW_LOGS_DIR Airflow logs directory. ${AIRFLOW_BASE_DIR}/logs
AIRFLOW_SCHEDULER_LOGS_DIR Airflow scheduler logs directory. ${AIRFLOW_LOGS_DIR}/scheduler
AIRFLOW_CONF_FILE Airflow configuration file. ${AIRFLOW_BASE_DIR}/airflow.cfg
AIRFLOW_WEBSERVER_CONF_FILE Airflow Webserver configuration file. ${AIRFLOW_BASE_DIR}/webserver_config.py
AIRFLOW_TMP_DIR Airflow directory temporary files. ${AIRFLOW_BASE_DIR}/tmp
AIRFLOW_DAGS_DIR Airflow data to be persisted. ${AIRFLOW_BASE_DIR}/dags
AIRFLOW_DAEMON_USER Airflow system user. airflow
AIRFLOW_DAEMON_GROUP Airflow system group. airflow

In addition to the previous environment variables, all the parameters from the configuration file can be overwritten by using environment variables with this format: AIRFLOW__{SECTION}__{KEY}. Note the double underscores.

Specifying Environment variables using Docker Compose

version: '2'

services:
  airflow:
    image: bitnami/airflow:latest
    environment:
      - AIRFLOW_FERNET_KEY=46BKJoQYlPPOexq0OhDZnIlNepKFf87WFwLbfzqDDho=
      - AIRFLOW_SECRET_KEY=a25mQ1FHTUh3MnFRSk5KMEIyVVU2YmN0VGRyYTVXY08=
      - AIRFLOW_EXECUTOR=CeleryExecutor
      - AIRFLOW_DATABASE_NAME=bitnami_airflow
      - AIRFLOW_DATABASE_USERNAME=bn_airflow
      - AIRFLOW_DATABASE_PASSWORD=bitnami1
      - AIRFLOW_PASSWORD=bitnami123
      - AIRFLOW_USERNAME=user
      - AIRFLOW_EMAIL=user@example.com

Specifying Environment variables on the Docker command line

docker run -d --name airflow -p 8080:8080 \
    -e AIRFLOW_FERNET_KEY=46BKJoQYlPPOexq0OhDZnIlNepKFf87WFwLbfzqDDho= \
    -e AIRFLOW_SECRET_KEY=a25mQ1FHTUh3MnFRSk5KMEIyVVU2YmN0VGRyYTVXY08= \
    -e AIRFLOW_EXECUTOR=CeleryExecutor \
    -e AIRFLOW_DATABASE_NAME=bitnami_airflow \
    -e AIRFLOW_DATABASE_USERNAME=bn_airflow \
    -e AIRFLOW_DATABASE_PASSWORD=bitnami1 \
    -e AIRFLOW_PASSWORD=bitnami123 \
    -e AIRFLOW_USERNAME=user \
    -e AIRFLOW_EMAIL=user@example.com \
    bitnami/airflow:latest

SMTP Configuration

To configure Airflow to send email using SMTP you can set the following environment variables:

  • AIRFLOW__SMTP__SMTP_HOST: Host for outgoing SMTP email. Default: localhost
  • AIRFLOW__SMTP__SMTP_PORT: Port for outgoing SMTP email. Default: 25
  • AIRFLOW__SMTP__SMTP_STARTTLS: To use TLS communication. Default: True
  • AIRFLOW__SMTP__SMTP_SSL: To use SSL communication. Default: False
  • AIRFLOW__SMTP__SMTP_USER: User of SMTP used for authentication (likely email). No defaults.
  • AIRFLOW__SMTP__SMTP_PASSWORD: Password for SMTP. No defaults.
  • AIRFLOW__SMTP__SMTP_MAIL_FROM: To modify the "from email address". Default: airflow@example.com

This would be an example of SMTP configuration using a GMail account:

  • docker-compose (application part):
  airflow:
    image: bitnami/airflow:latest
    environment:
      - AIRFLOW_FERNET_KEY=46BKJoQYlPPOexq0OhDZnIlNepKFf87WFwLbfzqDDho=
      - AIRFLOW_SECRET_KEY=a25mQ1FHTUh3MnFRSk5KMEIyVVU2YmN0VGRyYTVXY08=
      - AIRFLOW_EXECUTOR=CeleryExecutor
      - AIRFLOW_DATABASE_NAME=bitnami_airflow
      - AIRFLOW_DATABASE_USERNAME=bn_airflow
      - AIRFLOW_DATABASE_PASSWORD=bitnami1
      - AIRFLOW_PASSWORD=bitnami
      - AIRFLOW_USERNAME=user
      - AIRFLOW_EMAIL=user@email.com
      - AIRFLOW__SMTP__SMTP_HOST=smtp@gmail.com
      - AIRFLOW__SMTP__SMTP_USER=your_email@gmail.com
      - AIRFLOW__SMTP__SMTP_PASSWORD=your_password
      - AIRFLOW__SMTP__SMTP_PORT=587
    ports:
      - 8080:8080
  • For manual execution:
docker run -d --name airflow -p 8080:8080 \
    -e AIRFLOW_FERNET_KEY=46BKJoQYlPPOexq0OhDZnIlNepKFf87WFwLbfzqDDho= \
    -e AIRFLOW_SECRET_KEY=a25mQ1FHTUh3MnFRSk5KMEIyVVU2YmN0VGRyYTVXY08= \
    -e AIRFLOW_EXECUTOR=CeleryExecutor \
    -e AIRFLOW_DATABASE_NAME=bitnami_airflow \
    -e AIRFLOW_DATABASE_USERNAME=bn_airflow \
    -e AIRFLOW_DATABASE_PASSWORD=bitnami1 \
    -e AIRFLOW_PASSWORD=bitnami123 \
    -e AIRFLOW_USERNAME=user \
    -e AIRFLOW_EMAIL=user@example.com \
    -e AIRFLOW__SMTP__SMTP_HOST=smtp@gmail.com \
    -e AIRFLOW__SMTP__SMTP_USER=your_email@gmail.com \
    -e AIRFLOW__SMTP__SMTP_PASSWORD=your_password \
    -e AIRFLOW__SMTP__SMTP_PORT=587 \
    bitnami/airflow:latest

FIPS configuration in Bitnami Secure Images

The Bitnami Apache Airflow Docker image from the Bitnami Secure Images catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:

  • OPENSSL_FIPS: whether OpenSSL runs in FIPS mode or not. yes (default), no.

Notable Changes

Starting October 30, 2024

  • The Airflow container now supports running as a Web server, Scheduler or Worker component, so it's no longer necessary to combine this container image with bitnami/airflow-scheduler and bitnami/airflow-worker in order to use the CeleryExecutor.
  • The AIRFLOW_COMPONENT_TYPE environment variable was introduced to specify the component type. Current supported values are webserver, scheduler and worker, although it's planned to add soon support for dag-processor and triggerer components. The default value is webserver.

1.10.15-debian-10-r17 and 2.0.1-debian-10-r50

  • The size of the container image has been decreased.
  • The configuration logic is now based on Bash scripts in the rootfs/ folder.

Contributing

We'd love for you to contribute to this Docker image. 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.