Repository navigation
[BUG] docker compose run always printing status of containers #13882
Description
Description
docker compose run ... first prints the status of all the containers, for example:
[+] 8/8t 8/88
✔ Container project-postgres-1 Running 0.0s
✔ Container project-something-1 Running 0.0s
✔ Container project-graphql-1 Running 0.0s
✔ Container project-actions-1 Running 0.0s
✔ Container project-etl-1 Running 0.0s
✔ Container project-misc-1 Running 0.0s
✔ Container project-foobar-1 Running 0.0s
✔ Container project-smtpd-1 Running 0.0s
Container project-postgres-1 Waiting
Container project-postgres-1 Healthy
Container project-misc-run-c77002ad69e2 Creating
Container project-misc-run-c77002ad69e2 Created
Here the misc container depends on postgres so I can see some utility in showing the Waiting and Healthy lines (although they are duplicative – the same container already received a ✔ up above). However, the ✔ lines are noise. I don't know what the first line – [+] 8/8t 8/88 – means. Perhaps that block was added during debugging and accidentally committed?
Passing --no-deps eliminates the Waiting and Healthy lines but not the ✔ lines. Running docker compose --progress=quiet eliminates all lines, but this is perhaps too much. Setting COMPOSE_PROGRESS=quiet in the environment is definitely too much because it eliminates build output, etc.
I think this might have changed with the release of 5.2.0.
Steps To Reproduce
No response
Compose Version
Docker Compose version 5.2.0
Docker Environment
Client: Docker Engine - Community
Version: 29.6.1
Context: colima
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.35.0
Path: /opt/homebrew/lib/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: 5.2.0
Path: /opt/homebrew/lib/docker/cli-plugins/docker-compose
Server:
Containers: 14
Running: 13
Paused: 0
Stopped: 1
Images: 44
Server Version: 29.6.1
Storage Driver: overlayfs
driver-type: io.containerd.snapshotter.v1
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
/run/cdi
Discovered Devices:
cdi: lima-vm.io/rosetta=cached
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: e53c7c1516c3b2bff98eb76f1f4117477e6f4e66
runc version: v1.3.6-0-g491b69ba
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.8.0-100-generic
Operating System: Ubuntu 24.04.4 LTS
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 9.69GiB
Name: colima
ID: cb8b56b3-c3e6-42f7-aa06-011d432c53d4
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: false
Insecure Registries:
::1/128
127.0.0.0/8
Live Restore Enabled: false
Firewall Backend: iptables
EnableUserlandProxy: true
UserlandProxyPath: /usr/bin/docker-proxy
Anything else?
No response
Activity
fix(run): scope Running events to project.Services