Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

allow custom signals #230

Closed
nanassito opened this issue Mar 28, 2013 · 4 comments
Closed

allow custom signals #230

nanassito opened this issue Mar 28, 2013 · 4 comments

Comments

@nanassito
Copy link

At the moment when executing a docker stop instance docker send a sigterm and then a sigkill to the process running in the container. It would be nice to be able to configure which signals are sent and how long does docker wait before killing the process.

Use case for this feature :

  • We have n back-end jobs that takes a very long time (like video analysis)
  • We would like to scale down the number of back-ends as soon as possible
  • Therefore we would like one of our back-end to receive a sighup to exit as soon as possible (eg. finish its current task and then exit).
@creack
Copy link
Contributor

creack commented Mar 30, 2013

+1

1 similar comment
@titanous
Copy link
Contributor

👍

creack added a commit that referenced this issue Mar 31, 2013
@creack
Refactor container.Stop to handle custom timeout/signals (#230)
e26ab61
@creack creack mentioned this issue Mar 31, 2013
Closed
@vieux vieux mentioned this issue Jun 12, 2013
Merged
@shykes
Copy link
Contributor

shykes commented Jul 17, 2013

Cc @unclejack , for reference in your future dockerrun patches

@keeb-zz
Copy link
Contributor

keeb-zz commented Jul 20, 2013

This seems to have been merged. Closing

@keeb-zz keeb-zz closed this as completed Jul 20, 2013
@shykes shykes mentioned this issue Jul 26, 2013
Closed
thaJeztah pushed a commit to thaJeztah/docker that referenced this issue Jun 18, 2019
@andrewhsu
Merge pull request moby#230 from thaJeztah/18.09_backport_windows_tag
bb54c5b 
[18.09 backport] Consider WINDOWS_BASE_IMAGE_TAG override when setting Windows base image for tests
dperny pushed a commit to dperny/docker that referenced this issue Oct 18, 2021
@andrewhsu
Merge pull request moby#230 from thaJeztah/merge_upstream_sync
af31e5f 
[master] sync to upstream engine de86ba2
dperny pushed a commit to dperny/docker that referenced this issue Oct 18, 2021
@thaJeztah
Revert "Merge pull request moby#230 from thaJeztah/merge_upstream_sync"
373aeda 
This reverts commit af31e5f, reversing
changes made to 2d0b18e.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
dperny pushed a commit to dperny/docker that referenced this issue Oct 18, 2021
@andrewhsu
Merge pull request moby#232 from thaJeztah/revert_sync
d2f1bb5 
[master] Revert "Merge pull request moby#230 from thaJeztah/merge_upstream_sync"
dperny pushed a commit to dperny/docker that referenced this issue Oct 18, 2021
Revert "Revert "Merge pull request moby#230 from thaJeztah/merge_upst…
0795ad3 
…ream_sync""

This reverts commit 373aeda.

Conflicts:
	daemon/config/config.go
	daemon/info.go
	daemon/licensing.go
	daemon/licensing_test.go
	integration/service/create_test.go
	vendor.conf

Signed-off-by: Tibor Vass <tibor@docker.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@titanous @keeb-zz @shykes @creack @nanassito