compose/pkg
Nicolas De Loof 8fbda262bb build: error messages name the real remedy, not a removed builder
The classic-builder rejections said 'set DOCKER_BUILDKIT=1 to use
BuildKit', a leftover from the internal BuildKit builder removed in
af579ebd4. Since then BuildKit builds go through the buildx plugin:
compose falls back to the classic builder when BuildKit is disabled
(DOCKER_BUILDKIT=0) OR when buildx is not installed — so the advertised
fix does nothing for users who are simply missing buildx.

The five messages now state the actual requirement (buildx installed,
DOCKER_BUILDKIT not forced to 0), and the silent-fallback warning when
buildx is missing now says what the fallback implies instead of a bare
'requires buildx plugin to be installed'.

Part of #14074 (A: the code misdescribes its own structure).

Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
2026-08-27 11:05:09 +02:00
..
api feat(hooks): retain failed pre_start containers for post-mortem 2026-08-20 18:57:02 +02:00
bridge refactor: last gocognit candidates — bridge resources and TestViz 2026-08-18 13:37:48 +02:00
compose build: error messages name the real remedy, not a removed builder 2026-08-27 11:05:09 +02:00
dryrun remove buildx as a Go dependency 2026-08-25 17:27:26 +02:00
e2e build: error messages name the real remedy, not a removed builder 2026-08-27 11:05:09 +02:00
mocks chore(mocks): fix the stale mockgen invocation and pin its version 2026-08-20 15:16:43 +02:00
remote refactor: split ociRemoteLoader.Load pull and index resolution 2026-08-18 13:37:48 +02:00
utils
watch test(watch): cover the permission branches as root 2026-08-11 14:10:40 +02:00