From 5e39c6f6647fd748cc4cb0a22933273c5563d2a4 Mon Sep 17 00:00:00 2001 From: Brodie Kurczynski Date: Tue, 7 May 2019 15:50:09 -0700 Subject: [PATCH] Updated multi-stage build doc (#8769) Changed the 'as' keyword to 'AS' to match the Dockerfile reference docs here: https://docs.docker.com/engine/reference/builder/#from --- develop/develop-images/multistage-build.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/develop/develop-images/multistage-build.md b/develop/develop-images/multistage-build.md index 2f3ae15005..022a1741db 100644 --- a/develop/develop-images/multistage-build.md +++ b/develop/develop-images/multistage-build.md @@ -131,13 +131,13 @@ intermediate artifacts are left behind, and not saved in the final image. By default, the stages are not named, and you refer to them by their integer number, starting with 0 for the first `FROM` instruction. However, you can -name your stages, by adding an `as ` to the `FROM` instruction. This +name your stages, by adding an `AS ` to the `FROM` instruction. This example improves the previous one by naming the stages and using the name in the `COPY` instruction. This means that even if the instructions in your Dockerfile are re-ordered later, the `COPY` doesn't break. ```conf -FROM golang:1.7.3 as builder +FROM golang:1.7.3 AS builder WORKDIR /go/src/github.com/alexellis/href-counter/ RUN go get -d -v golang.org/x/net/html COPY app.go .