From 3ef52ed2b336997c447199aca25958c86b739e86 Mon Sep 17 00:00:00 2001 From: Brad Davidson Date: Fri, 2 Feb 2024 19:35:06 +0000 Subject: [PATCH] Fix ctr command examples Signed-off-by: Brad Davidson --- docs/installation/registry-mirror.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/installation/registry-mirror.md b/docs/installation/registry-mirror.md index 33672a8fe..c5162ee0b 100644 --- a/docs/installation/registry-mirror.md +++ b/docs/installation/registry-mirror.md @@ -117,5 +117,5 @@ You would then be able to pull those images from all cluster members, as long as The embedded registry is read-only, and cannot be pushed to directly using `docker push` or other common tools that interact with OCI registries. Images can be manually made available via the embedded registry by running `ctr -n k8s.io image pull` to pull an image, -or by loading image archives via the `ctr -n k8s.io import` or `ctr -n k8s.io load` commands. +or by loading image archives via the `ctr -n k8s.io image import` or `ctr -n k8s.io image load` commands. Note that the `k8s.io` namespace must be specified when managing images via `ctr` in order for them to be visible to the kubelet.