From 24ad7faf6dfe0b226306ebad481d532de5041e9d Mon Sep 17 00:00:00 2001
From: kurokobo <2920259+kurokobo@users.noreply.github.com>
Date: Tue, 26 Apr 2022 23:18:04 +0900
Subject: [PATCH] fix: replace k3s with absolute path

---
 registry/README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/registry/README.md b/registry/README.md
index 40c7303..9c118a5 100644
--- a/registry/README.md
+++ b/registry/README.md
@@ -204,13 +204,13 @@ EOF
 sudo systemctl restart k3s
 ```
 
-If this is successfully applied, you can check the applied configuration in the `config.registry` section of the following command. Be sure to use the `crictl` binary from k3s, otherwise you won't see your changes reflected in the `containerd` configuration used by k3s.
+If this is successfully applied, you can check the applied configuration in the `config.registry` section of the following command.
 
 ```bash
-sudo k3s crictl info
+sudo /usr/local/bin/k3s crictl info
 
 # With jq
-sudo k3s crictl info | jq .config.registry
+sudo /usr/local/bin/k3s crictl info | jq .config.registry
 ```
 
 If you want Kubernetes to be able to pull images directly from this private registry, alternatively you can also manually create `imagePullSecrets` for the Pod instead of writing your credentials in `auth` in `registries.yaml`. [Another guide about rate limiting on Docker Hub](../tips/dockerhub-rate-limit.md) explains how to use `ImagePullSecrets`.