Nicolas De loof
Nicolas De loof
IMHO there's some misunderstanding here. Compose does not control the build, it just configure buildx (vendored) to build required images. The fact a non-default builder won't store the base image...
@k1w1m8 that's what I mean: this isn't a docker compose feature, never has been. You just expect the builder to store base image in engine local cache, this isn't something...
@k1w1m8 this is not specific to compose, you have the same issue with a plain `docker build..`. This is really internal to the builder
> There is also the image: tags inside the compose files. (...) we'd like control of the downloaded base images to be consistent no matter if done via compose image...
image download during the Dockerfile build process, via buildkit, are store in the builder - when using the one backed by docker engine, this is actually the same as docker...
@k1w1m8 again, this is not related to compose: you will have the exact same issue using a plain `docker build ...`. Base image will be pulled by builder, and _may_...
Compose indeed is basically just docker build then docker run. And docker build is implemented by buildx, so this is the right place to report this issue. But as I...
please run `make spec` to get the single-page spec aligned with changes
Container log to use ANSI sequence obviously conflicts with Compose own formatter to set output. As compose treats logs line by line, it must _at least_ repeat this formatting on...