Skip to content

Commit b922732

Browse files
wkingwking
committed
Drop exec, pause, resume, and signal
All of these require state information to be shared between funC invocations (to map from a container ID to the cgroups/namespaces/etc.), and after today's meeting we may be backing away from that [1,2]. Even if we keep a requirement for sharing state between funC invocations, we don't want to specify these IPC-requiring commands until we have more clarity on that requirement in the spec. On systems like Solaris, the kernel maintains a registry of container IDs directly, so they don't need an external registry [3]. But without a consensus around the minimal amount of inter-process state sharing, we don't want to require container ID → state lookups in the command-line spec. Once we have more clarity on a minimal required mechanism (e.g. Julz's --state-file [4,5,6]), we can add them back in with an API that all runtimes can easily support (although runtimes are of course free to provide more convenient APIs as additional extensions). Pause, resume, and signal are still in the current lifecycle pull request [7], but I've requested they be removed until we have more clarity around the basic lifecycle [8]. [1]: http://ircbot.wl.linuxfoundation.org/meetings/opencontainers/2015/opencontainers.2015-12-02-18.01.html [2]: http://ircbot.wl.linuxfoundation.org/meetings/opencontainers/2015/opencontainers.2015-12-02-18.01.log.html#l-79 [3]: #3 (comment) [4]: #3 (comment) [5]: #3 (comment) [6]: #3 (comment) [7]: mrunalp/specs@bd549a2#diff-b84a8d65d8ed53f4794cd2db7e8ea731R48 [8]: https://github.com/opencontainers/specs/pull/231/files#r45532412 Signed-off-by: W. Trevor King <[email protected]> Reviewed-by: Mike Brown <[email protected]> Reviewed-by: Jesse Butler <[email protected]> Reviewed-by: Julian Friedman <[email protected]>
1 parent 933b55d commit b922732

1 file changed

Lines changed: 0 additions & 78 deletions

File tree

‎runtime.md‎

Lines changed: 0 additions & 78 deletions
Original file line numberDiff line numberDiff line change
@@ -67,84 +67,6 @@ $ echo $?
6767
42
6868
```
6969

70-
### exec
71-
72-
Runs a secondary process in the given container.
73-
74-
* *Options*
75-
* *`--process <PATH>`* Override `process.json` with an alternative path. The path may not support seeking (e.g. `/dev/fd/3`).
76-
* *Arguments*
77-
* *`<ID>`* The container ID to join.
78-
* *Standard streams:* The runtime must attach its standard streams directly to the application process without inspection.
79-
* *Exit code:* The runtime must exit with the application process's exit code.
80-
81-
If the main application (launched by `start`) dies, all other processes in its container will be killed [TODO: link to lifecycle docs explaining this].
82-
83-
Example:
84-
```sh
85-
# in a directory with a process.json that echos "goodbye" and exits 43
86-
$ funC exec hello-1
87-
goodbye
88-
$ echo $?
89-
43
90-
```
91-
92-
### pause
93-
94-
Pause all processes in a container.
95-
96-
* *Options*
97-
* *`--wait`* Block until the process is completely paused.
98-
Otherwise return immediately after initiating the pause, which may happen before the pause is complete.
99-
* *Arguments*
100-
* *`<ID>`* The container ID to join.
101-
* *Exit code:* 0 on success, non-zero on error.
102-
103-
Example:
104-
```sh
105-
$ funC pause --wait hello-1
106-
$ echo $?
107-
0
108-
```
109-
110-
### resume
111-
112-
Unpause all processes in a container.
113-
114-
* *Options*
115-
* *`--wait`* Block until the process is completely unpaused.
116-
Otherwise return immediately after initiating the unpause, which may happen before the unpause is complete.
117-
* *Arguments*
118-
* *`<ID>`* The container ID to join.
119-
* *Exit code:* 0 on success, non-zero on error.
120-
121-
Example:
122-
```sh
123-
$ funC resume hello-1
124-
$ echo $?
125-
0
126-
```
127-
128-
### signal
129-
130-
Sends a signal to the container.
131-
132-
* *Options*
133-
* *`--signal <SIGNAL>`* The signal to send.
134-
This must be one of the valid POSIX signals, although runtimes on non-POSIX systems must translate the POSIX name to their platorm's analogous signal.
135-
Defaults to TERM.
136-
* *Arguments*
137-
* *`<ID>`* The container ID to join.
138-
* *Exit code:* 0 on success, non-zero on error.
139-
A 0 exit status does not imply the process has exited (as it may have caught the signal).
140-
141-
Example:
142-
```sh
143-
$ funC signal --signal KILL hello-1
144-
$ echo $?
145-
0
146-
```
147-
14870
[posix-encoding]: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap06.html#tag_06_02
14971
[posix-lang]: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html#tag_08_02
15072
[posix-locale-encoding: http://www.unicode.org/reports/tr35/#Bundle_vs_Item_Lookup

0 commit comments

Comments
 (0)