--progress=plain option for docker build #3340

bateleurX · 2022-03-08T12:15:09Z

bateleurX
Mar 8, 2022

Similar to #3204

We are using Docker Buildx and Buildkit.
Both Buildkit and Buildx emit enormous outputs in CI environment. They write following messages per 0.1 second.
CI=true environment variable reduces messages in deploying phase, but doesn't affect docker messages.

example

[+] Building 0.0s (0/1)
[+] Building 0.1s (2/3)
 => [internal] load build definition from Dockerfile                       0.1s
 => => transferring dockerfile: 335B                                       0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
 => [internal] load metadata for docker.io/library/nginx:1.18.0            0.0s
[+] Building 0.3s (2/3)
 => [internal] load build definition from Dockerfile                       0.1s
 => => transferring dockerfile: 335B                                       0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
 => [internal] load metadata for docker.io/library/nginx:1.18.0            0.1s
[+] Building 0.4s (2/3)
 => [internal] load build definition from Dockerfile                       0.1s
 => => transferring dockerfile: 335B                                       0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
 => [internal] load metadata for docker.io/library/nginx:1.18.0            0.3s

They can be suppressed with --progress=plain option in docker build like this.

#1 [internal] load build definition from Dockerfile-nginx
#1 transferring dockerfile: 639B done
#1 DONE 0.0s

#2 [internal] load .dockerignore
#2 transferring context: 69B 0.0s done
#2 DONE 0.0s

#3 [internal] load metadata for public.ecr.aws/docker/library/nginx:1.20.2
#3 DONE 1.4s

If we cloud use --progress=option in copilot svc deploy, it will be useful in CI build.

efekarakus · 2022-03-08T15:40:47Z

efekarakus
Mar 8, 2022
Maintainer

Hi @bateleurX ! The feature request makes total sense, what do you think if we automatically set --progress=plain when CI=true instead of allowing configurability in the manifest file?