jasder
/
runc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

runtime: Remove start's "fails to run" monitoring 

The in-flight runC implementation just fires a signal at the container
[1,2].  It doesn't wait around to see if the signal has an effect, or if
it causes the container to crash, etc., etc.

[1]: 28126f8039/start.go (L29-L30)
[2]: 28126f8039/libcontainer/container_linux.go (L253-L258)

Signed-off-by: W. Trevor King <wking@tremily.us>
This commit is contained in:
W. Trevor King 2016-05-26 23:12:10 -07:00
parent c26f07c877
commit 9b47c1241c
1 changed files with 0 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
runtime.md
View File

@ -86,7 +86,6 @@ This operation MUST generate an error if it is not provided the container ID.
Attempting to start a container that does not exist MUST generate an error.
Attempting to start an already started container MUST have no effect on the container and MUST generate an error.
This operation MUST run the user-specified code as specified by [`process`](config.md#process-configuration).
If the runtime fails to run the code as specified, an error MUST be generated.
### Kill
`kill <container-id> <signal>`