This is an automated email from the ASF dual-hosted git repository.
jscheffl pushed a commit to branch v3-1-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/v3-1-test by this push:
new 6d992758cba [v3-1-test] fix: correct typos in
MANUALLY_BUILDING_IMAGES.md (#58761) (#58788)
6d992758cba is described below
commit 6d992758cba4e6c741c8b378ef57b539ad4997e0
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Thu Nov 27 19:54:32 2025 +0100
[v3-1-test] fix: correct typos in MANUALLY_BUILDING_IMAGES.md (#58761)
(#58788)
(cherry picked from commit 92055c8aa86d458476560f1d6ab7070f1834e7ac)
Co-authored-by: Leo Liao <[email protected]>
Co-authored-by: Tzu-ping Chung <[email protected]>
---
dev/MANUALLY_BUILDING_IMAGES.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev/MANUALLY_BUILDING_IMAGES.md b/dev/MANUALLY_BUILDING_IMAGES.md
index bd041842b49..18ba10dd210 100644
--- a/dev/MANUALLY_BUILDING_IMAGES.md
+++ b/dev/MANUALLY_BUILDING_IMAGES.md
@@ -46,7 +46,7 @@ directory. This can make the docker context very large when
building images, bec
is transferred to the docker daemon. In order to avoid this we have
.dockerignore where we exclude certain
paths from being treated as part of the context - similar to .gitignore that
keeps them away from git.
-If your context gets large you see a long (minutes) preliminary step before
dockeer build is run
+If your context gets large you see a long (minutes) preliminary step before
docker build is run
where the context is being transmitted.
You can see all the context files by running:
@@ -86,7 +86,7 @@ However, emulation is very slow - more than 10x slower than
hardware-backed buil
> for instructions on how to install and upgrade the plugin.
If you plan to build a number of images and have two hardware (AMD linux and
ARM Mac for example available in
-the same network, you need t set up a hardware builder that will build them in
parallel using both hardware
+the same network, you need to set up a hardware builder that will build them
in parallel using both hardware
options. This usually can be done with those two commands - providing that you
have HOST:PORT of the
remote hardware available to securely connect to.
