astro dev start
Start a local Airflow environment in Docker mode (default) or standalone mode (without Docker).
For more information, see Build and run a project locally.
Usage
Options
Examples
The following error can sometimes occur when the CLI tries to build your Astro Runtime image using Podman:
You can resolve this issue by exporting the BUILDAH_FORMAT environment variable to Podman:
Standalone mode
Standalone mode runs Airflow directly on your machine in a virtual environment, without Docker. Use it when Docker isn’t available or when you want a lighter-weight local setup.
To set standalone as the default mode for a project:
To use standalone mode for a single command:
The --standalone flag applies to a single command. If you start your environment with the flag instead of setting dev.mode, you must also pass --standalone to astro dev stop, astro dev restart, and astro dev kill. Without the flag, these commands run in Docker mode and don’t act on your standalone environment.
To switch back to Docker mode:
The following commands are not available in standalone mode:
astro dev buildastro dev upgrade-testastro dev compose-export
astro dev run --standalone is not supported. To run Airflow CLI commands in standalone mode, set standalone as the default mode first:
Dockerfile handling in standalone mode
Standalone mode runs Airflow in a virtual environment instead of building a Docker image, so it doesn’t run the build instructions in your Dockerfile. It ignores instructions such as RUN and COPY. If your project relies on these instructions to install system packages or add files to the image, adjust your project before you run it in standalone mode.
Standalone mode reads the FROM instruction to determine your Astro Runtime version, and therefore the Airflow version, for your environment. It supports both Airflow 2 (Astro Runtime 13.x) and Airflow 3 (Astro Runtime 3.x) projects.