mirror of https://github.com/containers/image.git
docs: rename manpages to *.5.md
Suffix the manpages accordingly to be placed in the correct manpage folder during package installation. Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
This commit is contained in:
parent
8befafed7d
commit
be915057aa
|
|
@ -0,0 +1,28 @@
|
||||||
|
% containers-certs.d(5)
|
||||||
|
|
||||||
|
# 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 `/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 examplary 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 <rothberg@redhat.com>
|
||||||
|
|
@ -1,34 +0,0 @@
|
||||||
% containers-certs.d(5)
|
|
||||||
|
|
||||||
# NAME
|
|
||||||
containers-certs.d - Directory for storing custom container-registry certficates
|
|
||||||
|
|
||||||
# DESCRIPTION
|
|
||||||
A custom certificate for a container registry can be configured by creating a directory under `/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 CA roots (i.e., `.crt` files) and one or more `<client>.{cert,key}` cert pairs.
|
|
||||||
If more than one root or pair is specified, they will be used in alpha-numerical order.
|
|
||||||
|
|
||||||
```
|
|
||||||
/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
|
|
||||||
```
|
|
||||||
|
|
||||||
### Creating Client Certificates
|
|
||||||
A client certificate pair can be generated via `openssl`:
|
|
||||||
|
|
||||||
```
|
|
||||||
$ openssl genrsa -out client.key 4096
|
|
||||||
$ openssl req -new -x509 -text -key client.key -out client.cert
|
|
||||||
```
|
|
||||||
|
|
||||||
# SEE ALSO
|
|
||||||
openssl(1)
|
|
||||||
|
|
||||||
# HISTORY
|
|
||||||
Feb 2019, Originally compiled by Valentin Rothberg <rothberg@redhat.com>
|
|
||||||
Loading…
Reference in New Issue