7.2

Table Of Contents
Containers can interact with both Docker Registry HTTP API V1 and V2 in the following manner:
V1 over HTTP
(unsecured, plain HTTP
registry)
You can freely search this kind of registry, but you must manually configure
each Docker host with the --insecure-registry flag to provision
containers based on images from insecure registries. You must restart the
Docker daemon after setting the property.
V1 over HTTPS Use behind a reverse proxy, such as NGINX. The standard implementation
is available through open source at https://github.com/docker/docker-
registry.
V2 over HTTPS The standard implementation is open sourced at
https://github.com/docker/distribution.
V2 over HTTPS with
basic authentication
The standard implementation is open sourced at
https://github.com/docker/distribution.
V2 over HTTPS with
authentication through
a central service
You can run a Docker registry in standalone mode, in which there are no
authorization checks. Supported third-party registries are JFrog Artifactory
and Harbor. Docker Hub is enabled by default for all tenants and is not
present in the registry list, but it can be disabled with a system property.
Note Docker does not normally interact with secure registries configured with certificates signed by
unknown authority. The container service handles this case by automatically uploading untrusted
certificates to all docker hosts and enabling the hosts to connect to these registries. If a certificate cannot
be uploaded to a given host, the host is automatically disabled.
Create and Manage Container Registries
You can configure multiple registries to gain access to both public and private images.
Registries are public or private stores from which you upload or download images. You can disable, edit,
or delete the registries that you created. The images shown in the Containers > Templates tab are
based on the registries that you define.
When you create or manage registries in the Existing Registries page, you can click the Credentials or
Certificate icons to add or manage credentials and certificates.
Prerequisites
n
Log in to the vRealize Automation console as a container administrator.
n
Verify that at least one host is configured and available for container network configuration.
Procedure
1 Click the Containers tab.
2 Click Templates
Configuring vRealize Automation
VMware, Inc. 312