Description
When using Ctrl+C to interrupt operations in the containerized CLP package runtime, the signal is not properly propagated to native containers launched inside the runtime container. This can leave long-running containers orphaned, particularly when compression jobs do not report a completion status.
Impact
- Orphaned containers continue running in the background
- Resource consumption from abandoned workloads
- Cleanup requires manual intervention to identify and stop orphaned containers
Context
This issue was identified during testing of the containerized runtime introduced in PR #1512, where CLI wrappers now run inside the clp-runtime Docker Compose service.
References
Description
When using Ctrl+C to interrupt operations in the containerized CLP package runtime, the signal is not properly propagated to native containers launched inside the runtime container. This can leave long-running containers orphaned, particularly when compression jobs do not report a completion status.
Impact
Context
This issue was identified during testing of the containerized runtime introduced in PR #1512, where CLI wrappers now run inside the
clp-runtimeDocker Compose service.References
sbinvia Docker Compose; Remove redundant assets from the package (resolves #1358). #1512sbinvia Docker Compose; Remove redundant assets from the package (resolves #1358). #1512 (comment)