CI config is relying on Docker builds from previous job to be available in next job, but this turns out to be not always true. From CircleCI docs:
Every layer built in a previous job will be accessible in the Remote Docker Environment. However, in some cases your job may run in a clean environment, even if the configuration specifies docker_layer_caching: true.
Instead, we'll build and push in the same job for trunk branch only.
CI config is relying on Docker builds from previous job to be available in next job, but this turns out to be not always true. From CircleCI docs:
Instead, we'll build and push in the same job for
trunkbranch only.