ubuntu/airflow repository overview

ubuntu/airflow is a rock for airflow maintained by Canonical⁠.

Apache Airflow is a platform to programmatically author, schedule, and monitor workflows. This rock packages Airflow built from source on Ubuntu 24.04 with Python and a wide set of providers pre-installed (Amazon, GCP, Kubernetes, MySQL, Postgres, and more), so common integrations work out of the box without requiring additional pip installation inside the container.

[Learn more about airflow⁠]

⁠Tags and Architectures

NOTE: These tags follow a specific naming convention that respects the concept of channels⁠.

⁠Get started

This rock's entrypoint is Pebble, a container-optimized init process that enables the orchestration of a collection of local service processes as an organized set.

[Learn more about Pebble⁠]

⁠Inspect

To view the Pebble services⁠ and checks⁠ defined in this rock:

docker run --rm ubuntu/airflow:3-24.04_edge plan

⁠Run

To run this rock, use any of the usual container runtimes, for example, docker:

docker run --name airflow-container \
    -p 8080:8080 -e AIRFLOW_HOME=/opt/airflow -v /path/to/dags:/opt/airflow/dags -v /path/to/airflow.cfg:/opt/airflow/airflow.cfg \
    ubuntu/airflow:3-24.04_edge

Pebble (PID 1) launches the airflow service, which runs airflow standalone. This initializes a local SQLite metadata database, creates a default admin user, and starts the webserver and scheduler in a single process group (intended for development use). The generated admin password is printed in the container logs. Access the Airflow web UI at http://localhost:8080⁠.

⁠Airflow service

The airflow service is configured with:

command: /usr/bin/airflow standalone
startup: enabled

airflow standalone initializes a local metadata DB, creates a default admin user, and starts the webserver, scheduler, and other core components in one process group (intended for development).

⁠Configuration & State

• Runtime state (AIRFLOW_HOME) lives at /opt/airflow. This includes airflow.cfg, airflow.db (Database by default for standalone), logs, and dags/.
• It is required to mount volumes to persist that data or to inject custom dags. For example: -v ./dags:/opt/airflow/dags -v ./airflow.cfg:/opt/airflow/airflow.cfg

⁠Providers

The rock is built from Airflow with many providers pre-installed (Amazon, GCP, Kubernetes, MySQL, Postgres, etc.), so common integrations work out of the box without requiring pip install inside the container.

⁠Full Configuration Reference:

Airflow offers a large number of configuration options that can be set via environment variables or airflow.cfg. For the complete list of configurable settings, consult the official configuration reference⁠

⁠Get logs

To view the logs of the running container, run:

docker exec airflow-container pebble logs

Or, for a specific service:

docker exec airflow-container pebble logs <service>

⁠Monitor health checks

Rocks may have predefined health checks that you can list by running:

docker exec airflow-container pebble checks

The overall health of your container can be inspected via:

docker exec airflow-container pebble health

⁠Configuration

⁠Environment variables

⁠Volumes

⁠Ports

[Report a bug⁠] [Contribute⁠]

Canonical is the provider of this container image. It is the user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within, as well as with Canonical’s IP Policy⁠.