Dockerfile Layer Invalidation Language Collocations
Practise the standard verbs for avoiding unwanted Dockerfile layer invalidation.
0 / 5 completed
1 / 5
Fill in: 'We ___ Dockerfile instructions so rarely-changing steps like dependency installs sit above frequently-changing source code.'
We 'order' instructions — the standard, simple collocation for sequencing Dockerfile steps. The other options are less idiomatic here.
2 / 5
Fill in: 'Copying the whole source tree before installing dependencies can ___ every layer below it rebuilt on any code edit.'
We say a bad COPY order will 'force' unnecessary rebuilds — the standard collocation for the resulting behaviour. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a package manifest separately before the rest of the source so dependency layers stay cached between builds.'
We 'copy' a file — the standard, established Docker collocation (COPY) for adding files into an image. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ build cache hit rates in CI to confirm a Dockerfile change didn't accidentally invalidate every layer.'
We 'track' a rate — the standard collocation for monitoring a metric over time. The other options aren't idiomatic here.
5 / 5
Fill in: 'We ___ a .dockerignore file so unrelated file changes never invalidate the build context checksum unnecessarily.'
We 'maintain' a file — the standard collocation for keeping a config file current. The other options aren't idiomatic here.