Codecov Report

Patch coverage: 100.00% and project coverage change: +0.10 🎉

Comparison is base (b0a35cc) 59.40% compared to head (6b91f4a) 59.51%.

@@            Coverage Diff             @@
##               v2   #10633      +/-   ##
==========================================
+ Coverage   59.40%   59.51%   +0.10%     
==========================================
  Files         107      107              
  Lines        9395     9403       +8     
==========================================
+ Hits         5581     5596      +15     
+ Misses       3240     3234       -6     
+ Partials      574      573       -1     

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

Would this fix allow for Ctrl+R to be sent to a container started with docker compose up? I'm trying to find if there are any open issues with regards to stdin and docker compose managed containers.

@g0t4 docker compose up is not interactive, it doesn't attach to a specific container, and as such won't forward signals to service(s). You can use docker compose kill -s [SIGNAL] SERVICE for this purpose

@ndeloof Hello sir, is this still true?

If a process is launched with docker compose up - there is no way for my image to be sent the shutdown signal?

Are there any ways to achieve it?

Ctrl+C or down command will send a SIGINT signal to your container, you can tweak signal being sent and timeout waiting for termination in your compose.yaml file, see https://github.com/compose-spec/compose-spec/blob/master/05-services.md#stop_grace_period