Skip to content

Commit 4a87a44

Browse files
committed
lifecycle: Allow multiple applications in one container
This makes joining a running container easy (it's just like launching the original application, although perhaps using different config files). Signed-off-by: W. Trevor King <[email protected]>
1 parent d83516e commit 4a87a44

File tree

1 file changed

+17
-13
lines changed

1 file changed

+17
-13
lines changed

lifecycle.md

Lines changed: 17 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -7,20 +7,24 @@ A typical lifecyle progresses like this:
77
1. There is no container or running application
88
2. A user tells the runtime to [create](#create) a container
99
3. The runtime creates the container
10-
4. A user tells the runtime to [start](#start-process) an application
11-
5. The runtime executes any [pre-start hooks](runtime.md#pre-start)
12-
6. The runtime executes the application
13-
7. The application is running
14-
8. A user tells the runtime to [stop](#stop) an application
15-
9. The runtime sends a termination signal to the application
16-
10. The application exits
17-
11. The runtime executes any [post-stop hooks](runtime.md#post-stop)
18-
12. A user tells the runtime to [destroy](#destroy) the container
19-
13. The runtime removes the container
20-
21-
With steps 8 and 9, the user is explicitly stopping the application
10+
4. Manage applications:
11+
1. A user tells the runtime to [start](#start-process) an application
12+
2. The runtime executes any [pre-start hooks](runtime.md#pre-start)
13+
3. The runtime executes the application
14+
4. The application is running
15+
5. A user tells the runtime to [stop](#stop) an application
16+
6. The runtime sends a termination signal to the application
17+
7. The application exits
18+
8. The runtime executes any [post-stop hooks](runtime.md#post-stop)
19+
5. A user tells the runtime to [destroy](#destroy) the container
20+
6. The runtime removes the container
21+
22+
With steps v and vi, the user is explicitly stopping the application
2223
(via the runtime), but it's also possible that the application could
23-
exit for other reasons. In that case we skip directly from 7 to 10.
24+
exit for other reasons. In that case we skip directly from iv to vii.
25+
26+
You can also repeat the application steps in 4 as many times as you
27+
want, to launch multiple applications inside the same container.
2428

2529
### Create
2630

0 commit comments

Comments
 (0)