potiuk commented on pull request #22304: URL: https://github.com/apache/airflow/pull/22304#issuecomment-1068885495
Hey everyone - here is my take on stronger language that we should IMHO put on the Docker-Compose Quick Start. I've been invovled in a number of issues raised by our users and honestly I think the "premise" of docker-compose that you can "just use it" and modify and you will be good, without really understanding of the "intricacies" of it does much more harm than good - giving the users false expectations on "how easy" it is to get airflow running with docker-compose. Yeah. Easy to start, Extremely difficult to diagnose and solve problems if you do not know exactly what you are doing. I think we should be very explicit that if user chooses docker-compose based on our quick start - the moment they touch the file, they are mostly on their own. I'd love to hear other's thoughts about it, but this is the experience I have with users who think that our "docker-compose" is on our website, means that we will help them to solve their "learn how docker-compose works" problems. Many times the comments I saw from the users was `But I am using the "official" docker-compose. It shoudl work!". I think this is false expectations and this PR is another attempt to be even clearer about the expectations users should have. -- 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]
