My CircleCI configuration has a job defined with a machine executor using docker_layer_caching. This currently works as expected using
docker build. However, when moving to a custom builder to target multiple platforms, I do not see subsequent runs using a cache. The documentation for this option does not say anything regarding using buildx.
The main change in the job is:
docker buildx create --use --name myname
docker buildx build …
It’s plausible to me that a custom builder may need to be configured in some way to leverage the cache that CircleCI is meant to add. Is there any advice on what that could look like?