You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/hosts.md
+10-5Lines changed: 10 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,13 @@
1
1
2
2
# Registry Configuration - Introduction
3
3
4
-
Configuring registries will be done by specifying (optionally) a `hosts.toml` file for
5
-
each desired registry host in a configuration directory. **Note**: Updates under this directory
6
-
do not require restarting the containerd daemon.
4
+
New and additional registry hosts config support has been implemented in containerd v1.5 for the `ctr`
5
+
client (the containerd tool for admins/developers), containerd image service clients, and CRI clients
6
+
such as `kubectl` and `crictl`.
7
+
8
+
Configuring registries, for these clients, will be done by specifying (optionally) a `hosts.toml` file for
9
+
each desired registry host in a configuration directory. **Note**: Updates under this directory do not
10
+
require restarting the containerd daemon.
7
11
8
12
## Registry API Support
9
13
@@ -17,9 +21,10 @@ Currently supported OCI Distribution version: **[v1.0.0](https://github.com/open
17
21
18
22
### Using Host Namespace Configs with CTR
19
23
20
-
When pulling via `ctr` use the `--hosts-dir` option:
24
+
When pulling a container image via `ctr` using the `--hosts-dir` option tells `ctr`
25
+
to find and use the host configuration files located in the specified path:
0 commit comments