Repository navigation
Add experimental opt-in Podman support to Breeze environment checks - #77189
Open
JLFinance25 wants to merge 1 commit into
Open
JLFinance25 wants to merge 1 commit into
JLFinance25 wants to merge 1 commit into
Conversation
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.
JLFinance25
requested review from
amoghrajesh,
ashb,
bugraoz93,
choo121600,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl,
potiuk and
vatsrahul1001
as code owners
November 17, 2026 05:34
|
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
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 --podmanswitch (as suggested in #54894) so thoseusers 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.buildfolder, 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:
uv run --project dev/breeze pytest dev/breeze/tests(2 selective-checks failures also fail on unmodified main in my shallow clone).prek runon the changed files passes.dockerwrapper 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?
Generated-by: Claude Code (Opus 5.5) following the guidelines; reviewed by the submitter.