Skip to main content
Version: 0.27

Astronomer CLI Release Notes


This document provides a summary of all changes made to the Astronomer CLI. For general product release notes, go to Astronomer Software Release Notes.

If you have any questions or a bug to report, don't hesitate to reach out to us via Slack or Intercom. We're here to help.


Release date: March 15, 2022

Bug fixes

  • Fixed an issue where astro dev logs and astro dev start didn't work when using custom Docker container names
  • Fixed an issue where astro deploy did not work when using Podman in specific circumstances
  • Fixed an issue where airflow_settings.yaml was not properly imported to the Airflow UI when running Astro in a local Podman environment
  • Fixed an issue where updating a Deployment's deployment type via astro deployment update would generate an error in the Software UI


Release date: February 15, 2022

Bug Fixes

  • Fixed an issue where environment variables in docker-compose.override.yml were not correctly applied after running astro dev start


Release date: January 21, 2022

Improvements to the Local Development Experience

Breaking Change

The latest version of the Astronomer CLI uses Docker engine 1.13.1 to run Airflow locally via astro dev. If you haven't done so already, ensure that your version of Docker Engine is at least 1.13.1 before upgrading the Astronomer CLI to v0.27.2. If your Docker Engine version is <1.13.1, then astro dev commands will not work on your local machine.

Astronomer CLI v0.27.2 includes several improvements to the local development experience:

  • You can now run astro dev start with Docker Buildkit enabled. This resolves a common issue where users with Docker Buildkit enabled experienced an error that prevented them from running this command.

  • You can now run a Triggerer in a local Airflow environment. This means that you can test DAGs that use deferrable operators locally before pushing them to a Deployment on Astronomer. Triggerer logs appear alongside Webserver and Scheduler logs when you run astro dev logs. Note that the Triggerer can run only in environments running Astronomer Certified 2.2.0+.

  • The Docker containers for the Scheduler, Webserver, and Triggerer now have standard names that persist after restarting your environment. You can check the names of these containers in your local Airflow environment by running astro dev ps:

    $ astro dev ps

    Name State Ports
    webserver running 8080
    triggerer running
    scheduler running
    0.27.2_a64c1a-postgres-1 running 5432

    To change the default names of these containers, run astro config set <airflow-component>.container_name <new-component-container-name>.

Additional Improvements

Bug Fixes

  • Fixed an issue where you could not run an Astronomer project via astro dev init/ astro dev start in a directory with certain characters in the directory name