From 6c14ecf870b383a15fcff94800d4d9b84915832e Mon Sep 17 00:00:00 2001 From: Lugano Abel Date: Wed, 23 Aug 2023 11:59:20 -0400 Subject: [PATCH] Fixed explanation error in second stage base image reference --- content/build/building/multi-stage.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/build/building/multi-stage.md b/content/build/building/multi-stage.md index 93c7b04952..70dd9c942b 100644 --- a/content/build/building/multi-stage.md +++ b/content/build/building/multi-stage.md @@ -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. \ No newline at end of file +The legacy builder processes `stage1`, even if `stage2` doesn't depend on it.