Continue printing log output after Ctrl-C has been pressed

[bfirsh]

When I run fig up and hit Ctrl-C, the log output stops immediately. It'd be useful to keep on printing log output until the process stops.

[sylvinus]

+1

[parshap]

👍

[matikucharski]

Any update on this?

[Dobiasd]

Just ran into the same problem.

Here is a minimal example to reproduce the issue:

---

Here is a service (python in that example) that prints something on SIGINT/SIGTERM.

printer.py:

import signal
import sys
import threading

def runner(stop_event):
    while not stop_event.wait(1):
        print('Hi.', flush=True)

stop_event = threading.Event()

def signal_handler(*_):
    stop_event.set()
    print('Bye.', flush=True)
    sys.exit(0)

signal.signal(signal.SIGINT, signal_handler)
signal.signal(signal.SIGTERM, signal_handler)

runner_thread = threading.Thread(target=runner, args=(stop_event,))
runner_thread.start()
runner_thread.join()

When running normally in the terminal and pressing CTRL+C, it works fine, i.e., the Bye. message is printed:

$ python3 printer.py 
Hi.
Hi.
^CBye.

However when running with Docker compose and CTRL+C-ing it, Bye. is never shown.

Dockerfile:

FROM python:3.7
ADD printer.py .
CMD [ "python", "printer.py" ]

docker-compose.yml:

version: '2.4'

services:
  printer:
    build:
      context: .
      dockerfile: Dockerfile

Terminal interaction:

$ docker-compose up
Creating network "compose_print_term_default" with the default driver
Creating compose_print_term_printer_1 ... done
Attaching to compose_print_term_printer_1
printer_1  | Hi.
printer_1  | Hi.
^CGracefully stopping... (press Ctrl+C again to force)
Stopping compose_print_term_printer_1 ... done

It would be really great if it could continue to print the log output instead.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because it had not recent activity during the stale period.

[Dobiasd]

This issue has been automatically closed because it had not recent activity during the stale period.

Oh, that's sad. For me, it's still an issue.

[Shawak]

Also having this problem.

[tomlagier]

Still an issue for me as well. Makes it very difficult to determine whether cleanup behavior is happening correctly or not.

[jkgeyti]

This seems like a genuine omission, and is still tracked in #2227 . Can it be reopened?