rpms/skopeo
7
0
Fork 0
Code Issues Pull Requests Releases Activity

Update to latest registries.conf man page

Browse Source 
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
This commit is contained in:
Daniel J Walsh 2018-07-30 08:11:53 -04:00
parent 66e950b038
commit b646a7f8a1
No known key found for this signature in database
GPG Key ID: A2DF901DABE2C028
1 changed files with 29 additions and 40 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

69
registries.conf.5.md
View File

@ -1,50 +1,39 @@
% registries.conf(5) System-wide registry configuration file % registries.conf(5) Container Registries Configuration File
% Brent Baude % Dan Walsh
% Aug 2017 % March 2018
# NAME ## NAME
registries.conf - Syntax of System Registry Configuration File registries.conf - Syntax of Container Registries configuration file
# DESCRIPTION ## DESCRIPTION
The REGISTRIES configuration file is a system-wide configuration file for container image The REGISTRIES configuration file specifies all of the available container registries for tools using shared container registries, but in a TOML format that can be more easily modified and versioned. `registries.conf` does not support recursive lists of registries. The default location for this configuration file is `/etc/containers/registries.conf`.
registries. The file format is TOML. The valid categories are: 'registries.search',
'registries.insecure', and 'registries.block'.
# FORMAT The only valid categories are: `registries.search`, `registries.insecure`, and `registries.block`.
The TOML_format is used to build a simple list format for registries under three
categories: `registries.search`, `registries.insecure`, and `registries.block`.
You can list multiple registries using a comma separated list.
Search registries are used when the caller of a container runtime does not fully specify the
container image that they want to execute. These registries are prepended onto the front
of the specified container image until the named image is found at a registry.
Insecure Registries. By default container runtimes use TLS when retrieving images ## FORMAT
from a registry. If the registry is not setup with TLS, then the container runtime The [TOML format][toml] is used as the encoding of the configuration file.
will fail to pull images from the registry. If you add the registry to the list of Every option and subtable listed here is nested under a global "registries" table.
insecure registries then the container runtime will attempt use standard web protocols to No bare options are used.
pull the image. It also allows you to pull from a registry with self-signed certificates.
Note insecure registries can be used for any registry, not just the registries listed
under search.
Block Registries. The registries in this category are are not pulled from when ## Examples
retrieving images. [registries.search]
registries = ['quay.io', 'docker.io', 'registries.unsafe.com', 'registry.fedoraproject.org', 'registry.access.redhat.com']
# EXAMPLE # If you need to access insecure registries, add the registry's fully-qualified name.
The following example configuration defines two searchable registries, one # An insecure registry is one that does not have a valid SSL certificate or only does HTTP.
insecure registry, and two blocked registries. [registries.insecure]
registries = ['registries.unsafe.com']
``` # If you need to block push access from a registry, uncomment the section below
[registries.search] # and add the registries fully-qualified name.
registries = ['registry1.com', 'registry2.com'] #
# Docker only
[registries.block]
registries = []
[registries.insecure] ## Files
registries = ['registry3.com'] /etc/conainers/registries.conf
[registries.block] ## HISTORY
registries = ['registry.untrusted.com', 'registry.unsafe.com'] March 2018, Originally compiled by Dan Walsh <dwalsh@redhat.com>
```
# HISTORY
Aug 2017, Originally compiled by Brent Baude <bbaude@redhat.com>
Jun 2018, Updated by Tom Sweeney <tsweeney@redhat.com>