`--quiet` mode failing when `DOCKER_BUILDKIT=1`

[amrishparmar]

Description

Steps to reproduce the issue:

1. create stub Dockerfile and docker-compose.yml, e.g.

   FROM hello-world
   

   services:
     hello:
       build:
         context: "."
         dockerfile: Dockerfile
   

2. Run docker-compose build --quiet with DOCKER_BUILDKIT=0 and DOCKER_BUILDKIT=1

Describe the results you received:

$ DOCKER_BUILDKIT=0 docker-compose build --quiet

$ DOCKER_BUILDKIT=1 docker-compose build --quiet
[+] Building 0.1s (5/5) FINISHED                                                                                                                             
 => [internal] load build definition from Dockerfile                                                                                                    0.0s
 => => transferring dockerfile: 61B                                                                                                                     0.0s
 => [internal] load .dockerignore                                                                                                                       0.0s
 => => transferring context: 2B                                                                                                                         0.0s
 => [internal] load metadata for docker.io/library/hello-world:latest                                                                                   0.0s
 => [1/1] FROM docker.io/library/hello-world                                                                                                            0.0s
 => exporting to image                                                                                                                                  0.0s
 => => exporting layers                                                                                                                                 0.0s
 => => writing image sha256:bb31f47d8cce4ac32588f855be49807af0926c794495faaf2cceee57f89e1ce9                                                            0.0s
 => => naming to docker.io/library/test_hello 

With DOCKER_BUILDKIT=0 (or omitted) docker-compose output is quiet With DOCKER_BUILDKIT=1 docker-compose output is noisy (not expected)

Describe the results you expected:

With DOCKER_BUILDKIT=0 (or omitted) docker-compose output is quiet With DOCKER_BUILDKIT=1 docker-compose output is quiet

Additional information you deem important (e.g. issue happens only occasionally):

Output of docker compose version:

docker-compose version 1.29.2, build 5becea4c

Output of docker info:

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.6.3-docker)
  scan: Docker Scan (Docker Inc., v0.9.0)

Server:
 Containers: 20
  Running: 19
  Paused: 0
  Stopped: 1
 Images: 7
 Server Version: 20.10.7
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 5b46e404f6b9f661a205e28d59c982d3634148f8
 runc version: v1.0.2-0-g52b36a2
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: default
 Kernel Version: 5.11.0-1021-aws
 Operating System: Ubuntu 20.04.3 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 15.26GiB
 Name: REDACTED
 ID: REDACTED
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

Additional environment details:

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically closed because it had not recent activity during the stale period.