[Solved] You want to build a Docker image for a Go application but keep it as small as possible. Which multi-stage Dockerfile snippet achieves this best? FROM golang:1.20 AS builder WORKDIR /app COPY . .... | Docker

Docker - Image Optimization

You want to build a Docker image for a Go application but keep it as small as possible. Which multi-stage Dockerfile snippet achieves this best?

FROM golang:1.20 AS builder
WORKDIR /app
COPY . .
RUN go build -o myapp

FROM alpine:latest
COPY --from=builder /app/myapp /usr/local/bin/myapp
CMD ["myapp"]

AThis build copies all source files to Alpine, increasing image size unnecessarily

BUsing Alpine as final image is bad because it lacks Go runtime

CThis multi-stage build compiles in golang image and copies only binary to Alpine, minimizing size

DYou should install Go in Alpine to build and run in one stage

Step-by-Step Solution

Solution:

Step 1: Understand multi-stage build purpose
Build stage uses full Go image; final stage uses minimal Alpine with only binary copied.
Step 2: Analyze final image contents
Only the compiled binary is copied, no source or build tools, keeping image small.
Final Answer:
This multi-stage build compiles in golang image and copies only binary to Alpine, minimizing size -> Option C
Quick Check:
Multi-stage build + minimal final image = small size [OK]

Quick Trick: Use multi-stage builds to copy only final artifacts [OK]

Common Mistakes:

Copying source files to final image
Installing build tools in final image
Building and running in same large image

Master "Image Optimization" in Docker

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More Docker Quizzes

You want to build a Docker image for a Go application but keep it as small as possible. Which multi-stage Dockerfile snippet achieves this best?

Step 1: Understand multi-stage build purpose

Step 2: Analyze final image contents

Final Answer:

Quick Check:

Want More Practice?