The PR updated - I think that solves the main problem I had with the
ballooning number of images :).  I guess with adding just one parallel
"slim" image to already existing images is far less controversial so I will
call for a lazy consensus :)

Thanks Jed It's quite obvious when you mentioned it, I wonder why I have
not thought about it before ).

This is how the convention will look like then.

+----------------+------------------+---------------------------------+--------------------------------------+
| Image          | Python           | Standard image                  |
Slim image                           |
+================+==================+=================================+======================================+
| Latest default | 3.7              | apache/airflow:latest           |
apache/airflow:slim-latest           |
| Default        | 3.7              | apache/airflow:X.Y.Z            |
apache/airflow:slim-X.Y.Z            |
| Latest         | 3.7,3.8,3.9,3.10 | apache/airflow:latest-pythonN.M |
apache/airflow:slim-latest-pythonN.M |
| Specific       | 3.7,3.8,3.9,3.10 | apache/airflow:X.Y.Z-pythonN.M  |
apache/airflow:slim-X.Y.Z-pythonN.M  |
+----------------+------------------+---------------------------------+--------------------------------------+

J.


On Thu, May 5, 2022 at 10:28 AM Jarek Potiuk <[email protected]> wrote:

> Yeah. Indeed it's almost no difference, that will simplify things a lot.
> Good Idea Jed. I will update the PR to reflect it :)
>
> On Thu, May 5, 2022 at 10:17 AM Jarek Potiuk <[email protected]> wrote:
>
>> Good point. Let me try :)
>>
>>
>> On Thu, May 5, 2022 at 5:57 AM Jed Cunningham <[email protected]>
>> wrote:
>>
>>> How much bigger would the image be if we included postgres, mysql, and
>>> mssql in the same image? That'd mean we'd have 4 vs 12 (ignoring the
>>> platform piece), and might be worth the tradeoff.
>>>
>>

Reply via email to