Open fho opened 1 year ago
Possibly related to
@thaJeztah thanks, that is actually same. Can I close this issue?
That specific issue was when the "cloud integration" (which is provided by the compose-cli
wrapper) is in use. It's possible that the same / similar issue exists in the docker
cli itself.
Are you using Docker Desktop? If so, does the problem also occur if you use com.docker.cli compose build
? (com.docker.cli
is the actual, "non-wrapped" docker
CLI, so skipping the cloud-integration binary).
That specific issue was when the "cloud integration" (which is provided by the
compose-cli
wrapper) is in use.
I see, different issue, thanks.
Are you using Docker Desktop?
No, I'm not using docker desktop.
Thanks for checking; for completeness, could you edit your first comment, and include the output of;
docker version
and
docker info
@thaJeztah updated, also added instructions how it can be verified
Thanks!
Description
Hello,
I'm wondering if it is on purpose that a TERM signal sent to the
docker
client process does not terminate the plugin it started. This causes for example when runningdocker compose build
and sending a TERM signal to thedocker
process` the compose plugin process continues to run.Are there scenarions for plugins where it's desirable for the process continue running after the docker-client process has terminated? Or should
SysProcAttr.Pdeathsig
be actually set for the started plugins?docker version:
docker info:
How to Reproduce
Create the following executable bash-script to act as docker-plugin: ~/.docker/cli-plugins/docker-test
docker test
process.docker/cli-plugins/docker-test
process still runs, it doesRelated to: https://github.com/docker/compose/issues/10634#issuecomment-1573388511