From d53bcba99149b25a5b46365e06852cbc97e5556c Mon Sep 17 00:00:00 2001 From: JoeWrightss Date: Tue, 11 Dec 2018 22:13:03 +0800 Subject: [PATCH] Fix some typo errors Signed-off-by: JoeWrightss --- pkg/server/image_pull.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pkg/server/image_pull.go b/pkg/server/image_pull.go index 3461b493a..56b05e8e9 100644 --- a/pkg/server/image_pull.go +++ b/pkg/server/image_pull.go @@ -61,11 +61,11 @@ import ( // 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? // -// 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. // // 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)? // // 3) The cri plugin only exposes "READY" (successfully pulled and unpacked) images