[BUG] Compose does not observe the BUILDKIT_PROGRESS environement variable

Description

Buildkit provides a --progress option which can also be set via the BUILDKIT_PROGRESS environment variable..

The --progress flag is effectively observed by Compose, but not the environment variable. For consistency and ease of configuration it would be nice if it did.

Steps To Reproduce

Run docker compose build --progress=plain
Enjoy the simpler output in environments where TERM=dumb;
Try and configure it for good by setting BUILDKIT_PROGRESS=plain;
But docker compose build is back to fancy output.

Compose Version

Docker Compose version v2.31.0-desktop.2

Docker Environment

Client:
 Version:    27.4.0
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  ai: Ask Gordon - Docker Agent (Docker Inc.)
    Version:  v0.5.1
    Path:     /Users/steph/.docker/cli-plugins/docker-ai
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.19.2-desktop.1
    Path:     /Users/steph/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.31.0-desktop.2
    Path:     /Users/steph/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.37
    Path:     /Users/steph/.docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Beta) (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/steph/.docker/cli-plugins/docker-desktop
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /Users/steph/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.27
    Path:     /Users/steph/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     /Users/steph/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.4.0
    Path:     /Users/steph/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/steph/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.15.1
    Path:     /Users/steph/.docker/cli-plugins/docker-scout

Server:
 Containers: 11
  Running: 6
  Paused: 0
  Stopped: 5
 Images: 41
 Server Version: 27.4.0
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 CDI spec directories:
  /etc/cdi
  /var/run/cdi
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 472731909fa34bd7bc9c087e4c27943f9835f111
 runc version: v1.1.13-0-g58aa920
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.10.14-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 8
 Total Memory: 7.654GiB
 Name: docker-desktop
 ID: 1acf2a23-42d5-4b07-9600-038408ecf200
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Labels:
  com.docker.desktop.address=unix:///Users/steph/Library/Containers/com.docker.docker/Data/docker-cli.sock
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

Anything else?

No response

The fix in #12458 doesn't seem to work.

There is a comment that explains it won't work due to the --progress option having a default value of "auto", yet the code in the fix checks it is "" which will never return true.

I'm on Compose: v2.38.1-desktop.1 and this still doesn't work for me. That is I still get fancy output with docker compose build when BUILDKIT_PROGRESS is set to plain.

I am also still experiencing this, on Compose v2.38.2. I suggest this issue be reopened.

$> docker compose version        
Docker Compose version 2.38.2

$> docker version    
Client: Docker Engine - Community
 Version:           28.3.2
 API version:       1.47 (downgraded from 1.51)
 Go version:        go1.24.5
 Git commit:        578ccf607d
 Built:             Wed Jul  9 12:04:02 2025
 OS/Arch:           darwin/arm64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          27.4.0
  API version:      1.47 (minimum version 1.24)
  Go version:       go1.22.10
  Git commit:       92a8393
  Built:            Sat Dec  7 10:39:01 2024
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.7.24
  GitCommit:        88bf19b2105c8b17560993bee28a01ddc2f97182
 runc:
  Version:          1.2.2
  GitCommit:        v1.2.2-0-g7cb3632
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

I am also still experiencing this, on Compose v2.38.2. I suggest this issue be reopened.

$> docker compose version        
Docker Compose version 2.38.2

$> docker version    
Client: Docker Engine - Community
 Version:           28.3.2
 API version:       1.47 (downgraded from 1.51)
 Go version:        go1.24.5
 Git commit:        578ccf607d
 Built:             Wed Jul  9 12:04:02 2025
 OS/Arch:           darwin/arm64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          27.4.0
  API version:      1.47 (minimum version 1.24)
  Go version:       go1.22.10
  Git commit:       92a8393
  Built:            Sat Dec  7 10:39:01 2024
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.7.24
  GitCommit:        88bf19b2105c8b17560993bee28a01ddc2f97182
 runc:
  Version:          1.2.2
  GitCommit:        v1.2.2-0-g7cb3632
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Same, BUILDKIT_PROGRESS is not working for docker compose build / docker compose up --build at v2.38.2.

More so, changing from v2.38.2 to v2.39.x changed my output to plain by default in the terminal.

docker info

Client: Docker Engine - Community
 Version:    28.3.2
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.25.0
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.38.2
    Path:     /home/user/.docker/cli-plugins/docker-compose

Server:
 Containers: 26
  Running: 17
  Paused: 0
  Stopped: 9
 Images: 118
 Server Version: 28.3.2
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 CDI spec directories:
  /etc/cdi
  /var/run/cdi
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 nvidia runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 05044ec0a9a75232cad458027ca83437aae3f4da
 runc version: v1.2.5-0-g59923ef
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.6.87.2-microsoft-standard-WSL2
 Operating System: Ubuntu 22.04.5 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 7.757GiB
 Name: DESKTOP-TTP757E
 ID: 0e6a9e8e-5b9e-4049-baf9-1efaf7f3d139
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  ::1/128
  127.0.0.0/8
 Live Restore Enabled: false

fix(ci): resolve pnpm approve-builds hang and Node.js 24 action warning

ci: add GitHub Actions CI pipeline (unit + integration tests) (#8)

Navigation Menu

Repository navigation

[BUG] Compose does not observe the BUILDKIT_PROGRESS environement variable #12457

Description

Steps To Reproduce

Compose Version

Docker Environment

Anything else?

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[BUG] Compose does not observe the BUILDKIT_PROGRESS environement variable #12457

Description

Description

Steps To Reproduce

Compose Version

Docker Environment

Anything else?

Activity

dkubb commented on May 29, 2025

razola commented on Jul 7, 2025

molguin92 commented on Jul 23, 2025

ToshY commented on Jul 25, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions