containers not receiving stop signal

[dankuri]

Description

When stopping containers either manually through docker stop or with compose through docker compose down/stop, containers don't receive the stop signal, even when specifying one. So, containers only stop after a timeout, when docker sends SIGKILL. Only option to send the stop signal is using docker exec <container_name> kill -15 <pid>. I've checked if there's a similar issue on Linux with native Docker and on MacOS using OrbStack, and there was no such problem, so I suppose it's specific to Colima.

Version

colima version 0.6.8
git commit: 9b0809d

runtime: docker
arch: x86_64
client: v25.0.3
server: v24.0.5
limactl version 0.20.1
qemu-img version 8.2.1
Copyright (c) 2003-2023 Fabrice Bellard and the QEMU Project developers

Operating System

• macOS Intel <= 13 (Ventura)
• macOS Intel >= 14 (Sonoma)
• Apple Silicon <= 13 (Ventura)
• Apple Silicon >= 14 (Sonoma)
• Linux

Output of colima status

INFO[0000] colima is running using QEMU
INFO[0000] arch: x86_64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/dankuri/.colima/default/docker.sock

Reproduction Steps

1. docker run -d --rm --name "test-signal" alpine top
2. docker stop test-signal - will wait about 10 seconds to kill the container
3. docker exec test-signal kill -15 1 - will stop the container immediately

Expected behaviour

Containers being able to receive stop signals.

Additional context

No response

[Henri Dickson]

same issue here, with vmType: vz