potiuk commented on issue #35255:
URL: https://github.com/apache/airflow/issues/35255#issuecomment-1784280819
> > That is expected that is why it is a slim image.
> > You need provide additional dependencies (Debian or/and Python packages)
by your own
>
> I thought it should have enough dependencies to start, though. If the user
writes DAGs that need certain providers it would make sense to be installed at
that point. Anyhow, thanks for clarifying
I am very curious, because I always assume our users are making resonable
assumptions based on documentation available to them. Where did you draw this
assumption from @RonaldGalea ?
Or maybe you missed that statement in the documentation? I really would
like to get it clearer for our users to understand what they are doing and I
assume the users are making reasonable assumptions based on the docs we write.
Could you explain how do you understand this chapter in the docs and why you
thought slim image is good to start even if it is expained you should add what
you need and even points you to the documentation?
> You can also use “slim” images that contain only core airflow and are
about half the size of the “regular” images but you need to add all the
[Reference for package
extras](https://airflow.apache.org/docs/apache-airflow/stable/extra-packages-ref.html)
and providers that you need separately via [Building the
image](https://airflow.apache.org/docs/docker-stack/build.html#build-build-image).
My goal is to make clearer, so I would like to understand where the
assumption is for. But be aware that I will ask you to click "Suggest a change
on this page" and propose a change on this page when you say it's not clear -
so maybe just start a PR right away if you think you can improve it to be
clearer and help other to better undertand 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]
