Skip to content

Add experimental opt-in Podman support to Breeze environment checks - #77189

Open
JLFinance25 wants to merge 1 commit into
apache:mainfrom
JLFinance25:breeze-podman-54894
Open

JLFinance25 wants to merge 1 commit into
apache:mainfrom
JLFinance25:breeze-podman-54894

Conversation

@JLFinance25

Copy link
Copy Markdown

Breeze currently exits as soon as it detects Podman, even for users who are happy to try it.
This adds a persistent breeze setup config --podman switch (as suggested in #54894) so those
users can get past the environment checks. It is a first step only.

When the switch is on and Podman is detected, Breeze prints an "experimental" warning, skips the
Docker version check (Podman's Docker-compatible CLI reports the Podman version, which cannot be
compared with the minimum Docker version) and runs the remaining checks (docker compose v2,
filesystem, entrypoint permissions) as before. With the switch off (default) Breeze still exits,
and now tells the user about the switch. Docker users are not affected.

The setting is stored like --worktree-isolation: a marker file in the main checkout's .build
folder, shared by all worktrees.

Not in this PR: building the images with Podman/BuildKit and a CI job running Breeze on Podman.
Those can build on this switch in follow-ups.

Testing:

  • New unit tests for the environment-check branches and for the config switch.
  • uv run --project dev/breeze pytest dev/breeze/tests (2 selective-checks failures also fail on unmodified main in my shallow clone).
  • prek run on the changed files passes.
  • Checked with a fake docker wrapper that reports itself as Podman. I have not yet tried it on a real Podman machine; feedback from someone who runs Podman is welcome.

related: #54894


Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

Generated-by: Claude Code (Opus 5.5) following the guidelines; reviewed by the submitter.

Breeze exits when it detects Podman, so users who want to try it cannot get past the
environment checks. A persistent setup config switch lets them opt in while Docker users
keep the existing behaviour.
@boring-cyborg

boring-cyborg Bot commented Nov 17, 2026

Copy link
Copy Markdown

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide
Here are some useful points:

  • Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
  • In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example Dag that shows how users should use it.
  • Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
  • Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
  • Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
  • Be sure to read the Airflow Coding style.
  • Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
    Apache Airflow is a community-driven project and together we are making it better 🚀.
    In case of doubts contact the developers at:
    Mailing List: dev@airflow.apache.org
    Slack: https://s.apache.org/airflow-slack

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant