JLFinance25 opened a new pull request, #77189: URL: https://github.com/apache/airflow/pull/77189
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? - [X] Yes (please specify the tool below) Generated-by: Claude Code (Opus 5.5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions); reviewed by the submitter. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
