Stop containers on interrupts

[eszpotanski]

Currently, when CTRL-C is used, Bazel sends SIGKILL to subprocesses, which only kills script process, but not Docker container.

This PR fixes this behavior, by enabling graceful-termination and handling SIGTERM signal.

[oharboe]

rework the code a bit to leave fewer questions and surprises

[oharboe]

Rework so that the handler is installed only when the container is running?

#!/bin/bash

# Function to handle SIGTERM signal
cleanup() {
    echo "Stopping container..."
    # Command to stop the container gracefully
    docker stop <container_name_or_id>
    exit 0
}

# Main
echo "Starting container..."
# Command to start your container, for example:
# docker run -d --name <container_name> <image_name>
docker run -d --name my_container my_image

# Wait until the container is either running or stopped
while true; do
    container_status=$(docker inspect -f '{{.State.Status}}' my_container)
    if [[ "$container_status" == "running" || "$container_status" == "exited" ]]; then
        break
    fi
    sleep 1
done

# Registering the cleanup function to handle SIGTERM
trap cleanup SIGTERM

# Wait for the script to be terminated
echo "Script is running. Press Ctrl+C to stop the container gracefully."
while true; do
    sleep 1
done

[eszpotanski]

In this case, SIGTERM can be received after docker run and before trap, then signal won't be handled, but container will be at least created.

I recreated this approach and tested it on BoomTile_synth, where a lot of containers are created, and usually at least one created container remained, but all running containers were stopped and removed.

Current solution stops and removes all containers created during bazel build.

If you prefer to add handler only when container is running and possibly not remove all created containers, I will commit these changes.