Skip to content

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

@molguin92

Description

@molguin92

Description

Buildkit provides ways of configure non-pretty (plain) build progress output through either a runtime flag (--progress=plain) or via an environment variable (BUILDKIT_PROGRESS=plain). Compose currently ignores the environment variable.

Support for the environment variable was supposed to be added in #12458 (released in Compose v2.33.0). This didn't work, and was then supposed to be fixed in #12894 (released in Compose v2.37.0). This again does not seem to work.

Steps To Reproduce

  1. Run a Compose stack using the BUILDKIT_PROGRESS=plain environment variable:
    BUILDKIT_PROGRESS=plain docker compose up
  2. Expected output: plaintext build and stack output, equivalent to running Compose with the --progress=plain flag.
  3. Actual output: pretty output with paging, colors, and multiple output streams writing to the terminal at the same time.

Compose Version

$> docker-compose version && docker compose version
Docker Compose version 2.38.2
Docker Compose version 2.38.2

Docker Environment

Client: Docker Engine - Community
 Version:    28.3.2
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.26.1
    Path:     /opt/homebrew/lib/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  2.38.2
    Path:     /opt/homebrew/lib/docker/cli-plugins/docker-compose

Server:
 Containers: 5
  Running: 0
  Paused: 0
  Stopped: 5
 Images: 126
 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
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 88bf19b2105c8b17560993bee28a01ddc2f97182
 runc version: v1.2.2-0-g7cb3632
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.8.0-62-generic
 Operating System: Ubuntu 24.04.2 LTS
 OSType: linux
 Architecture: aarch64
 CPUs: 6
 Total Memory: 15.58GiB
 Name: colima
 ID: 89601753-b543-4b7b-b5d6-b538bfa0ec99
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 34
  Goroutines: 76
  System Time: 2025-07-23T11:26:33.205427892-07:00
  EventsListeners: 0
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

Anything else?

This issue is effectively a re-opening/duplicate of issue 12457.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions