0

I init the latest kubernetes v1.25.2 with kubeadm, containerd as runtime.

Then config /etc/containerd/certs.d/my_registry:5000/hosts.toml in order to pull images from the private registry.

Command like this:

$ crictl pull my_registry:5000/hello-world:latest

The result is successful! But my registry requires account/password when using 'docker pull'.

Why does this happen?

wujinbin
  • 1
  • 2

1 Answers1

0

crictl is only using your container runtime. In your case, it is using containerd to actually do the pull. That means if you already have the configuration for containerd to authenticate, that will work out of the box with crictl.

How authentication for containerd works is lined out here and you can check if that is what you are actually using with the following command:

cat /etc/crictl.yaml

If that file does not exist, you will use the defaults, which are deprecated.

Rick Rackow
  • 1,490
  • 8
  • 19
  • I didn't store the credential of private registry anywhere. 1. containerd registry configuration: `$ cat /etc/containerd/certs.d/my_registry:5000/hosts.toml server = "http://my_registry:5000" [host."http://my_registry:5000"] capabilities = ["pull", "resolve"]` 2. crictl configuration: `$ cat /etc/crictl.yaml runtime-endpoint: "unix:///run/containerd/containerd.sock" image-endpoint: "unix:///run/containerd/containerd.sock" timeout: 0 debug: false pull-image-on-create: false disable-pull-on-run: false` – wujinbin Oct 06 '22 at 14:25