This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 8a9951e36b7 Docs: remove duplicated Docker image documentation (#60201)
8a9951e36b7 is described below
commit 8a9951e36b7e1b960545f6b8855ad226e7e58ef0
Author: shubhamkoti <[email protected]>
AuthorDate: Wed Jan 7 16:38:37 2026 +0530
Docs: remove duplicated Docker image documentation (#60201)
Co-authored-by: Shubham Koti <[email protected]>
---
docker-stack-docs/README.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docker-stack-docs/README.md b/docker-stack-docs/README.md
index a275d3d565a..920950e8488 100644
--- a/docker-stack-docs/README.md
+++ b/docker-stack-docs/README.md
@@ -41,7 +41,7 @@ You can find the following images there (Assuming Airflow
version `3.2.0`):
Those are "reference" regular images. They contain the most common set of
extras, dependencies and providers that are
often used by the users and they are good to "try-things-out" when you want to
just take Airflow for a spin,
-You can also use "slim" images that contain only core airflow and are about
half the size of the "regular" images
+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).
@@ -61,7 +61,7 @@ default extras/providers installed are not used by everyone,
sometimes others ex
are needed, sometimes (very often actually) you need to add your own custom
dependencies,
packages or even custom providers. You can learn how to do it in [Building the
image](https://airflow.apache.org/docs/docker-stack/build.html#build-build-image).
-The production images are build in DockerHub from released version and release
candidates. There
+The production images are built in DockerHub from released version and release
candidates. There
are also images published from branches but they are used mainly for
development and testing purpose.
See [Airflow Git
Branching](https://github.com/apache/airflow/blob/main/contributing-docs/10_working_with_git.rst#airflow-git-branches)
for details.
