From a7b070da3f7c537bae5eeb3cf0d236dd8640fc1e Mon Sep 17 00:00:00 2001 From: CoprDistGit Date: Thu, 1 Aug 2024 13:50:14 +0000 Subject: automatic import of containers-common --- containers-certs.d.5.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 containers-certs.d.5.md (limited to 'containers-certs.d.5.md') diff --git a/containers-certs.d.5.md b/containers-certs.d.5.md new file mode 100644 index 0000000..828ff76 --- /dev/null +++ b/containers-certs.d.5.md @@ -0,0 +1,28 @@ +% containers-certs.d 5 Directory for storing custom container-registry TLS configurations + +# NAME +containers-certs.d - Directory for storing custom container-registry TLS configurations + +# DESCRIPTION +A custom TLS configuration for a container registry can be configured by creating a directory under `$HOME/.config/containers/certs.d` or `/etc/containers/certs.d`. +The name of the directory must correspond to the `host:port` of the registry (e.g., `my-registry.com:5000`). + +## Directory Structure +A certs directory can contain one or more files with the following extensions: + +* `*.crt` files with this extensions will be interpreted as CA certificates +* `*.cert` files with this extensions will be interpreted as client certificates +* `*.key` files with this extensions will be interpreted as client keys + +Note that the client certificate-key pair will be selected by the file name (e.g., `client.{cert,key}`). +An exemplary setup for a registry running at `my-registry.com:5000` may look as follows: +``` +/etc/containers/certs.d/ <- Certificate directory +└── my-registry.com:5000 <- Hostname:port + ├── client.cert <- Client certificate + ├── client.key <- Client key + └── ca.crt <- Certificate authority that signed the registry certificate +``` + +# HISTORY +Feb 2019, Originally compiled by Valentin Rothberg -- cgit v1.2.3