[BUG] Docker compose spams terminal while in progress

Open mlava-sn opened this issue 2 years ago • 5 comments

Description

When running commands like docker compose start, stop, up, down, and maybe others, my terminal gets spammed with lines that are normally just overwritten. I don't know enough to say whether it's just one of these again, but feel free to close this if it's a duplicate:

https://github.com/docker/compose/issues/8547
https://github.com/docker/compose/issues/8753
https://github.com/docker/compose/issues/8800
https://github.com/docker/compose/issues/10256

Steps To Reproduce

Create a new folder with a docker-compose.yml file like so:

services:
  db:
    image: mongo
  nginx:
    image: nginx

Run docker compose up -d. (I chose detached to avoid mixing the log information from nginx mongo with the test results).

Compose Version

Docker Compose version v2.21.0

Docker Environment

Client: Docker Engine - Community
 Version:    24.0.7
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.11.2
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.21.0
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 141
  Running: 0
  Paused: 0
  Stopped: 141
 Images: 173
 Server Version: 24.0.7
 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: 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 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: d8f198a4ed8892c764191ef7b3b06d8a2eeb5c7f
 runc version: v1.1.10-0-g18a0cb0
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
 Kernel Version: 5.15.133.1-microsoft-standard-WSL2
 Operating System: Ubuntu 20.04.6 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 15.57GiB
 Name: PF17VFZ7
 ID: S265:YF6B:PLEM:62QL:4D4K:B2L5:REVN:UCOJ:BVPC:JCFJ:SLGH:5F4A
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support

Anything else?

As noted in the kernel version, I am running Ubunti in WSL2 on Windows. Specifically Windows 10 Enterprise edition 22h2 with wsl verion 2.0.9.0. I installed docker and the docker compose plugin from the download.docker.com repo as described in this article.

If I downgrade, 2.17.2 is the earliest version I see listed for me that has the same issue. 2.16.0 does not have this issue.

test > apt list -a docker-compose-plugin
Listing... Done
docker-compose-plugin/focal,now 2.21.0-1~ubuntu.20.04~focal amd64 [installed]
docker-compose-plugin/focal 2.20.2-1~ubuntu.20.04~focal amd64
docker-compose-plugin/focal 2.19.1-1~ubuntu.20.04~focal amd64
docker-compose-plugin/focal 2.18.1-1~ubuntu.20.04~focal amd64
docker-compose-plugin/focal 2.17.3-1~ubuntu.20.04~focal amd64
docker-compose-plugin/focal 2.17.2-1~ubuntu.20.04~focal amd64
docker-compose-plugin/focal 2.16.0-1~ubuntu.20.04~focal amd64
<and more...>

Dec 07 '23 04:12 mlava-sn