potiuk commented on issue #27690: URL: https://github.com/apache/airflow/issues/27690#issuecomment-1317163994
Buildkit is available for building images for > 3 years (as far as I remember) in all docker versions released since and it can be enabled by setting `DOCKER_BUILDKIT=1` variable (this is what the solution I linked to does if you look closely). And it is explicitly described in our changelog here https://airflow.apache.org/docs/docker-stack/changelog.html#airflow-2-3 We even figured out recently how to use buildking in engine-less `colima` (documentation of it is being contributed soon by one of the contributors who tried it recently). We only switched to use it after more than 2 years of trying an experimenting with it and after it became available in all docker versions that you might possibly imagine to run (I specifically hold on with the switch waiting for a long time to pass and making sure all operating systems people would like to use have it. > Having documentation that covers this use case and tech stack would be beneficial to increasing Airflow usage. Absolutely. By all means. I recommend you to try to figure it out on your own and if you think others would benefit from your investigation, I heartily recommend you @MohnJadden to improve our documentation and describe how to do it (like more than 2000 other contributors did when they found that they could help others solving some of their specific problems). It is super easy - you go to our docs in the place you think it should be added you click "Suggest a change on this page" and it will open a PR where you will be able to add appropriate instructions. No development needed - it will take less time than even responding to that comment, and I heartily recommend this route for you. We have more than 2000 contributors in Airflow and most of them were users like you who got a free software, lacked some documentation, found a solution and proposed a PR with their findings so that others can benefit from that. This is the least you can do as a contribution back for the software you get for free which is built and maintained by the community. If you won't find a solution - I recommend you create an issue in Azure Container Registry and ask for this capability. This is their problem of not supporting it, not ours if you cannot enable it. Maybe they need to improve their documentation, or enable this feature, or maybey you are doing something wrong, but this is the case between you and them and there is no way Airflow can base their decision on some platform sticking to technology that is more than 3 years old. If they do, then I think personally you should consider switching to something else. But I serioulsy doubt it and - since you are paid user - i believe if you reach out to them they will help you to understand how to do it. -- 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]
