Fix some typo errors
Signed-off-by: JoeWrightss <zhoulin.xie@daocloud.io>
This commit is contained in:
parent
5a80f333d4
commit
d53bcba991
@ -61,11 +61,11 @@ import (
|
|||||||
// if we saw an image without snapshots or with in-complete contents during startup,
|
// if we saw an image without snapshots or with in-complete contents during startup,
|
||||||
// should we re-pull the image? Or should we remove the entry?
|
// should we re-pull the image? Or should we remove the entry?
|
||||||
//
|
//
|
||||||
// yanxuean: We cann't delete image directly, because we don't know if the image
|
// yanxuean: We can't delete image directly, because we don't know if the image
|
||||||
// is pulled by us. There are resource leakage.
|
// is pulled by us. There are resource leakage.
|
||||||
//
|
//
|
||||||
// 2) Containerd suggests user to add entry before pulling the image. However if
|
// 2) Containerd suggests user to add entry before pulling the image. However if
|
||||||
// an error occurrs during the pulling, should we remove the entry from metadata
|
// an error occurs during the pulling, should we remove the entry from metadata
|
||||||
// store? Or should we leave it there until next startup (resource leakage)?
|
// store? Or should we leave it there until next startup (resource leakage)?
|
||||||
//
|
//
|
||||||
// 3) The cri plugin only exposes "READY" (successfully pulled and unpacked) images
|
// 3) The cri plugin only exposes "READY" (successfully pulled and unpacked) images
|
||||||
|
Loading…
Reference in New Issue
Block a user