This repository has been archived by the owner on Jan 25, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 108
Stop
Kowshik Prakasam and Pieter Noordhuis edited this page Feb 28, 2013
·
1 revision
Stops a container.
Once a container is stopped, warden does not allow spawning new processes inside the container. It is possible to copy files in to and out of a stopped container. It is only when a container is destroyed that its filesystem is cleaned up.
Warden stops a container by sending the processes running inside it the SIGTERM
signal.
It then waits for the processes to terminate before returning a response.
If one or more processes do not terminate within 10 seconds,
the warden server sends these processes the SIGKILL
signal,
killing them ungracefully.
-
handle
: Container handle. -
background
: Return a response immediately instead of waiting for the container to be stopped. -
kill
: Send SIGKILL instead of SIGTERM.
Empty.
- When
handle
does not refer to a container.
package warden;
message StopRequest {
required string handle = 1;
optional bool background = 10 [default = false];
optional bool kill = 20 [default = false];
}
message StopResponse {
}