Merge pull request #18012 from Hopertz/Hopertz-patch-1

Fixed explanation error in second stage base image reference
This commit is contained in:
David Karlsson authored and GitHub committed 2023-08-24 10:18:06 +02:00
commit eaf191bb8a
1 file changed
+2 -2
+2 -2
View File
@@ -56,7 +56,7 @@ None of the build tools required to build the application are included in the
resulting image.
How does it work? The second `FROM` instruction starts a new build stage with
the `alpine:latest` image as its base. The `COPY --from=0` line copies just the
the `scratch` image as its base. The `COPY --from=0` line copies just the
built artifact from the previous stage into this new stage. The Go SDK and any
intermediate artifacts are left behind, and not saved in the final image.
@@ -213,4 +213,4 @@ Removing intermediate container bbc025b93175
Successfully built 09fc3770a9c4
```
The legacy builder processes `stage1`, even if `stage2` doesn't depend on it.
The legacy builder processes `stage1`, even if `stage2` doesn't depend on it.