[BUG] logs -f is not terminated by Ctrl-C / SIGINT #13118
Description
Description
This behavior is new with Docker Compose shipped with Docker 28.3.3. It is not seen in the Compose shipped with 28.3.2
Run docker compose logs -f service and hit Ctrl-C. The log display stops, but does not terminate. A second Ctrl-C terminates it, with exit code 255
docker compose logs service does not show this: If Ctrl-C is hit during log display, Compose exits as expected.
docker logs -f container does not show this behavior: Ctrl-C exits as expected.
Expected behavior: Ctrl-C / SIGINT terminates a logs -f display
Steps To Reproduce
See above
Compose Version
`Docker Compose version v2.39.1`
Docker Environment
Client: Docker Engine - Community
Version: 28.3.3
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.26.1
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.39.1
Path: /usr/libexec/docker/cli-plugins/docker-compose
Server:
Containers: 26
Running: 25
Paused: 0
Stopped: 1
Images: 42
Server Version: 28.3.3
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: systemd
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
/var/run/cdi
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 05044ec0a9a75232cad458027ca83437aae3f4da
runc version: v1.2.5-0-g59923ef
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.1.0-37-amd64
Operating System: Debian GNU/Linux 12 (bookworm)
OSType: linux
Architecture: x86_64
CPUs: 12
Total Memory: 125.4GiB
Name: rpc3-a
ID: 37efb9cd-cf8d-4491-acb9-7173e9f77d13
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: false
Insecure Registries:
::1/128
127.0.0.0/8
Live Restore Enabled: false
Anything else?
No response