You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: runtime.md
+36Lines changed: 36 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,9 +90,45 @@ $ echo $?
90
90
0
91
91
```
92
92
93
+
### kill
94
+
95
+
[Send a signal][kill] to the container process.
96
+
97
+
**Arguments*
98
+
**`<ID>`* The container being signaled.
99
+
**Options*
100
+
**`--signal <SIGNAL>`* The signal to send (defaults to `TERM`).
101
+
The runtime MUST support `TERM` and `KILL` signals with [the POSIX semantics][posix-signals].
102
+
The runtime MAY support additional signal names.
103
+
On platforms that support [POSIX signals][posix-signals], the runtime MUST implement this command using POSIX signals.
104
+
On platforms that do not support POSIX signals, the runtime MAY implement this command with alternative technology as long as `TERM` and `KILL` retain their POSIX semantics.
105
+
Runtime authors on non-POSIX platforms SHOULD submit documentation for their TERM implementation to this specificiation, so runtime callers can configure the container process to gracefully handle the signals.
106
+
**Standard streams:*
107
+
**stdin:* The runtime MUST NOT attempt to read from its stdin.
108
+
**stdout:* The handling of stdout is unspecified.
109
+
**stderr:* The runtime MAY print diagnostic messages to stderr, and the format for those lines is not specified in this document.
110
+
**Exit code:* Zero if the signal was successfully sent to the container process and non-zero on errors.
111
+
Successfully sent does not mean that the signal was successfully received or handled by the container process.
112
+
113
+
#### Example
114
+
115
+
```
116
+
# in a bundle directory with a process ignores TERM
0 commit comments