gtxu opened a new issue, #71390:
URL: https://github.com/apache/airflow/issues/71390

   ### Under which category would you file this issue?
   
   Providers
   
   ### Apache Airflow version
   
   N/A
   
   ### What happened and how to reproduce it?
   
   Currently, the Airflow documentation implies or states that podman is 
supported as a container engine for the Breeze development environment.[See 
here](https://github.com/apache/airflow/blob/655740bb98282ca64d5bde2aeec65da8c56b1930/contributing-docs/03a_contributors_quick_start_beginners.rst?plain=1#L42)
 However, as highlighted and addressed in PR #58599, Podman is not yet fully 
supported, and users are now actively warned when Breeze detects it.
   Also in related issue #
   Leaving the documentation in its current state may mislead new contributors 
or developers attempting to set up their local environment using Podman.
   
   ### What you think should happen instead?
   
   Update the relevant sections of the Breeze documentation in 
`contributing-docs/03a_contributors_quick_start_beginners.rst`. And/or a 
statement of current Podman support status will help.
   
   ### Operating System
   
   _No response_
   
   ### Deployment
   
   None
   
   ### Apache Airflow Provider(s)
   
   _No response_
   
   ### Versions of Apache Airflow Providers
   
   N/A
   
   ### Official Helm Chart version
   
   Not Applicable
   
   ### Kubernetes Version
   
   _No response_
   
   ### Helm Chart configuration
   
   _No response_
   
   ### Docker Image customizations
   
   _No response_
   
   ### Anything else?
   
   This is a change to document only.
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to