`ansible-navigator run`: Control C Does Not Hault Container Execution in stdout Mode

[AndrewJackson2020]

ISSUE TYPE

• Bug Report

SUMMARY

Control C Does Not Hault Container Execution in stdout Mode for ansible-navigator run command

ANSIBLE-NAVIGATOR VERSION

>  ansible-navigator --version
ansible-navigator 25.12.0

CONFIGURATION

---
ansible-navigator:
  ansible:
    inventory:
      entries:
      - inventory
  execution-environment:
    container-engine: docker
    enabled: true
    environment-variables:
      pass:
        - VAULT_TOKEN
    image: {redacted}.com/{redacted}/{redacted}:latest
    pull:
       policy: always
    container-options:
      - '--entrypoint='
      - '--network=host'
      - '--user=root'
  mode: stdout
  logging:
    level: debug
  playbook-artifact:
    enable: true
    save-as: playbook-artifacts/{playbook_name}-artifact-{time_stamp}.json

LOG FILE

STEPS TO REPRODUCE

1. Run ansible navigator run in stdout mode
2. Mash control C. Console will stop printing to stdout
3. run docker ps or ps aux | grep ansible-playbook to see that container is still executing
4. run docker --attach log to view stdout of running process

EXPECTED RESULTS

Control-C should immediately hault container execution

ACTUAL RESULTS

container continues executing ansible-playbook command unbeknownst to the user

ADDITIONAL INFORMATION