Layer caching of convenience images

Build Environment
1

I have tested building a docker image for my needs, alternately with FROM cimg/python:3.11 and FROM python:3.11-bookworm-slim.

the from cimg image is 2.8GB in size, while the from: python:3.11-bookworm-slim image is 700MB.

However, pulling the larger image appears faster as I’m always noticing that there is a substantial amount of layers already available on the host.

Is this behavior something I can count on in all cases? Is it documented anywhere?

2

Details regarding the caching of container images can be found here

which states

The Docker images used for CircleCI jobs are automatically cached on the server infrastructure where possible.

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.