Stop containers when SIGINT is sent (like in docker-compose)

[arthrp]

Is your feature request related to a problem? Please describe.
When you press Ctrl-C in terminal running podman-compose, your containers are still left running. In contrast, docker-compose intercepts the SIGINT and powers down all containers.

Describe the solution you'd like
Same behavior as with docker-compose, stop all containers started by podman-compose up.

Additional context
Since podman-compose often acts as drop-in replacement for docker-compose, similar behavior would be beneficial.

[mokibit]

This issue was fixed by #1148, and I can no longer reproduce it.

Copying the reproduction trial #112 (comment) for convenience:

1. Versions:

podman-compose version 1.5.0
podman version 5.4.2

2. compose.yml File (keeps services running indefinitely):

services:
  test1:
    image: busybox
    command: tail -F test
  test2:
    image: busybox
    command: tail -F test

Commands executed:
podman-compose up (running up in the foreground)
CTRL+C

Partial output of CTRL+C command:

<...>
^CCaught SIGINT or Ctrl+C, shutting down...
Shutting down gracefully, please wait...
podman stop -t 10 podman-compose_test2_1
podman stop -t 10 podman-compose_test1_1
WARN[0010] StopSignal SIGTERM failed to stop container podman-compose_test1_1 in 10 seconds, resorting to SIGKILL 
exit code: 137
WARN[0010] StopSignal SIGTERM failed to stop container podman-compose_test2_1 in 10 seconds, resorting to SIGKILL 
exit code: 137
Sending termination signal
podman-compose_test1_1
exit code: 1
podman-compose_test2_1
exit code: 1

podman ps -a shows that all running containers have exited.
It is evident that podman-compose now works like docker-compose and forcefully stops all running containers when CTRL+C is pressed.

Please update podman-compose to its latest version, and it should work as expected.
If you encounter any other similar issues, please open a new bug report.

@p12tic this issue can be closed.

[p12tic]

Thanks, closing.