Practise the standard verbs for building efficient Docker multi-stage images.
0 / 5 completed
1 / 5
Fill in: 'We ___ a multi-stage build to strip dev dependencies, rather than shipping a bloated image nobody actually needs in production.'
We 'use a multi-stage build' — the standard, simple collocation for separating build and runtime layers in Docker. The other options are less idiomatic here.
2 / 5
Fill in: 'Copying the entire build context into the final stage can ___ the image carrying source files it never actually needs at runtime.'
We say a broad copy will 'leave' the image carrying unnecessary files — the standard, natural collocation for the resulting bloat. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the final stage from a minimal base image, rather than one that drags in tooling nobody actually runs in production.'
We 'build a stage' — the standard, simple collocation for constructing the runtime layer from a minimal image. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every image size against the previous build in CI, rather than letting bloat creep in without anyone actually noticing.'
We 'check size' — the standard, simple collocation for comparing image size between builds. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ layer caching order deliberately, rather than a Dockerfile that rebuilds dependencies on every actual code change.'
We 'order layers' — the standard, simple collocation for arranging Dockerfile instructions for cache efficiency. The other options aren't idiomatic here.