fix some typos
Signed-off-by: fate-grand-order <chenjg@harmonycloud.cn>
This commit is contained in:
parent
696e88c813
commit
8ce64b2000
5 changed files with 5 additions and 5 deletions
|
@ -41,7 +41,7 @@ may be exported for access via corresponding _services_.
|
|||
## Modules
|
||||
|
||||
In addition to the subsystems have, we have several components that may cross
|
||||
subsystem boundaries, referened to as components. We have the following
|
||||
subsystem boundaries, referenced to as components. We have the following
|
||||
components:
|
||||
|
||||
- __*Executor*__: The executor implements the actual container runtime.
|
||||
|
|
|
@ -5,7 +5,7 @@ While containerd is a daemon that provides API to manage multiple containers, th
|
|||
|
||||
## containerd
|
||||
|
||||
The daemon provides an API to manage multiple containers. It can handle locking in process where needed to cordinate tasks between subsystems. While the daemon does fork off the needed processes to run containers, the shim and runc, these are re-parented to the system's init.
|
||||
The daemon provides an API to manage multiple containers. It can handle locking in process where needed to coordinate tasks between subsystems. While the daemon does fork off the needed processes to run containers, the shim and runc, these are re-parented to the system's init.
|
||||
|
||||
## shim
|
||||
|
||||
|
|
|
@ -13,7 +13,7 @@ unit and unmounted as a unit.
|
|||
From an architecture perspective, components produce mounts and runtime
|
||||
executors consume them.
|
||||
|
||||
More imaginitive use cases include the ability to virtualize a series of mounts
|
||||
More imaginative use cases include the ability to virtualize a series of mounts
|
||||
from various components without ever having to create a runtime. This will aid
|
||||
in testing and implementation of satellite components.
|
||||
|
||||
|
|
|
@ -22,7 +22,7 @@ func TestBasicEvent(t *testing.T) {
|
|||
|
||||
ctx = WithTopic(ctx, "content")
|
||||
// simulate sub-operations with a separate topic, on the content store
|
||||
G(ctx).Post(ctx, fmt.Sprintf("received sha:256"))
|
||||
G(ctx).Post(ctx, fmt.Sprint("received sha:256"))
|
||||
|
||||
G(ctx).Post(ctx, fmt.Sprintf("unpack layer %v", layer))
|
||||
|
||||
|
|
|
@ -37,7 +37,7 @@ func (tx *transaction) begin(ctx context.Context, poster Poster) *transaction {
|
|||
}
|
||||
|
||||
// post the transaction started event
|
||||
poster.Post(ctx, child.makeTransactionEvent("begin")) // tranactions are really just events
|
||||
poster.Post(ctx, child.makeTransactionEvent("begin")) // transactions are really just events
|
||||
|
||||
return child
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue