potiuk commented on issue #17566: URL: https://github.com/apache/airflow/issues/17566#issuecomment-897460105
@pukaleashish -. I assume you are talking about Airflow images. Your (quite rude and not something that is expected in our community to be honest) request is invalid on many levels and I recommend you next time before you post any such request, you do at lest a minimum of research, before you make bold statements like that and demand ETA on a free product, that you make use of and pay no money for. I advise you should be more careful next time when you make such requests as you risk to be ignored and not taken seriously. Please spend a little time time on trying to understand airflow and images you are using. We have plenty of documentation and information available for you to try to understand before you send such a request.. Airflow on its own does not build on buster. The Airflow reference Image uses Debian buster as a base. and it always uses the latest buster available for those python version (3.6, 3.7, 3.8, 3.9). Airflow docker "reference" images (available in `apache/airflow" DockerHub - https://hub.docker.com/repository/docker/apache/airflow) are (at the moment they are built) built using the latest available images released then (including latest security patches). As of Airflow 2.1.2 we build 3.6, 3.7, 3.8, 3.9 versions. This is all nicely described in our user documentation https://airflow.apache.org/docs/docker-stack/index.html and in the image there is a standard "documentation url" label that contains link to that documentation, so you can very easily find it. You can find there the naming convention we use for the images and you can find out for example that (for example) there is the latest released `apache/airflow:2.1.2-python3.9` image which is based on latest debian buster 3.9 if you want to use it. We do not normally re-release airflow images for "past" versions, The reference image that we release is released at the time of release of airflow and normally is not updated any more. However when we release a new version (for example 2.1.3) we always use the latest available buster images for all versions. However if you want to rebuild the image using the newer buster images as base you can freely do so by building a custom image. Some examples here: https://airflow.apache.org/docs/docker-stack/build.html#examples-of-image-customizing - so if you want to get (for example 2.1.2 image build usine a newer version of buster image released in the meantime, you can do it easily on your own (you just need to get airflow 2.1.2 sources).: ``` docker build . \ --build-arg PYTHON_BASE_IMAGE="python:3.9-slim-buster" \ --build-arg AIRFLOW_VERSION="2.1.2" \ --tag "my-latest-airflow:2.1.2" ``` If you wish to get deeper and understand a bit more about the images you can see this document here: https://github.com/apache/airflow/blob/main/IMAGES.rst - describing some "whys" for the images as well as you can watch my talk about production docker images of Airflow from last year's Airflow Summit: https://www.youtube.com/watch?v=wDr3Y7q2XoI - it's not necessary if you want to just use the image, but you might find it useful if you care about your image and it's security so that you know you can (and should) build your image when you care about it. Kindly provide an ETA on when you are able to digest it and try it and come back to us if you have further questions after you read all the information. -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
