vbatts/containerd
1
0
Fork 0
Code Pull requests Releases Activity

fix some typos

Browse source 
Signed-off-by: Aaron.L.Xu <likexu@harmonycloud.cn>
This commit is contained in:
Aaron.L.Xu 2017-02-21 14:56:44 +08:00
parent e0b1736aa4
commit a3cae915c3
5 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

2
design/data-flow.md
View file

@ -5,7 +5,7 @@ images, hiding many details and complexity. This document intends to shed light
on that complexity and detail how a "pull" operation will look from the
perspective of a containerd user. We use the _bundle_ as the target object in
this workflow, and walk back from there to describe the full process. In this
context, we describe bothing pulling an image and creating a bundle from that
context, we describe both pulling an image and creating a bundle from that
image.
With containerd, we redefine the "pull" to comprise the same set of steps

2
design/lifecycle.md
View file

@ -11,4 +11,4 @@ The daemon provides an API to manage multiple containers. It can handle locking
Each container has its own shim that acts as the direct parent of the container's processes. The shim is responsible for keeping the IO and/or pty master of the container open, writing the container's exit status for containerd, and reaping the container's processes when they exit. Since the shim owns the container's pty master, it provides an API for resizing.
Overall, a container's lifecycle is not tied to the containerd daemon. The daemon is a management API for multiple container whoms lifecycle is tied to one shim per container.
Overall, a container's lifecycle is not tied to the containerd daemon. The daemon is a management API for multiple container whose lifecycle is tied to one shim per container.