From b5fc7846c465c10d9dfd4f0c150571c78e1a12b2 Mon Sep 17 00:00:00 2001 From: Mike Brown Date: Mon, 26 Jul 2021 14:55:44 -0500 Subject: [PATCH] adding a little more clarity Signed-off-by: Mike Brown --- docs/hosts.md | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/docs/hosts.md b/docs/hosts.md index d713af9ca..6af51727e 100644 --- a/docs/hosts.md +++ b/docs/hosts.md @@ -1,9 +1,13 @@ # Registry Configuration - Introduction -Configuring registries will be done by specifying (optionally) a `hosts.toml` file for -each desired registry host in a configuration directory. **Note**: Updates under this directory -do not require restarting the containerd daemon. +New and additional registry hosts config support has been implemented in containerd v1.5 for the `ctr` +client (the containerd tool for admins/developers), containerd image service clients, and CRI clients +such as `kubectl` and `crictl`. + +Configuring registries, for these clients, will be done by specifying (optionally) a `hosts.toml` file for +each desired registry host in a configuration directory. **Note**: Updates under this directory do not +require restarting the containerd daemon. ## Registry API Support @@ -17,9 +21,10 @@ Currently supported OCI Distribution version: **[v1.0.0](https://github.com/open ### Using Host Namespace Configs with CTR -When pulling via `ctr` use the `--hosts-dir` option: +When pulling a container image via `ctr` using the `--hosts-dir` option tells `ctr` +to find and use the host configuration files located in the specified path: ``` -ctr images pull --hosts-dir "/etc/containerd/certs.d" +ctr images pull --hosts-dir "/etc/containerd/certs.d" myregistry.io:5000/image_name:tag ``` ### CRI