potiuk commented on issue #15635: URL: https://github.com/apache/airflow/issues/15635#issuecomment-1099966824
For example this one: https://github.com/apache/airflow/pkgs/container/airflow%2Fmain%2Fprod%2Fpython3.7/19115034?tag=latest  Generally all the "dev" images of our are following the scheme: * ghcr.io/apache/airflow/main/prod/pythonX.Y * ghcr.io/apache/airflow/main/ci/pythonX.Y Following the naming convention we have for those: https://github.com/apache/airflow/blob/main/IMAGES.rst#naming-conventions You can always retag the latest image to a regular airflow one if you want to use some more familiar names: ``` docker pull ghcr.io/apache/airflow/main/prod/python3.7 docker tag ghcr.io/apache/airflow/main/prod/python3.7 apache/airflow:latest ``` Note that X.Y >= 3.7 because we dropped Python 3.6 in main and it is not refreshed any more. We only build and refresh the "latest" image for multi-platform. They are automatically refreshing after successful `main` build - so the images often reflect the latest "main" (unless we are in a period of fixing some `main` failures because of dependencies update - then they might be few commits behind). Those are the images that `breeze` uses, thus the naming convention is different than the "release" images which are published on GitHub. We do not publish multi-platform images there yet. I proposed to start releasing the experimental multi-platform images to DockerHub as well (we could do it for one of the betas/rcs of 2.3.0) - the tooling we have is ready for it - but I have not received any answers yet :) - feel free to comment if you think it is a good idea: https://lists.apache.org/thread/pqhks390dkso9x668gbnvjq6k6wv8h9h -- 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]
