Merge pull request #3754 from rancher/dnoland1-patch-1

Changing "Docker" registry reference to "container"
This commit is contained in:
Billy Tat
2022-01-03 16:29:49 -08:00
committed by GitHub
@@ -3,7 +3,7 @@ title: Configuring a Global Default Private Registry
weight: 40
---
You might want to use a private Docker registry to share your custom base images within your organization. With a private registry, you can keep a private, consistent, and centralized source of truth for the container images that are used in your clusters.
You might want to use a private container registry to share your custom base images within your organization. With a private registry, you can keep a private, consistent, and centralized source of truth for the container images that are used in your clusters.
There are two main ways to set up private registries in Rancher: by setting up the global default registry through the **Settings** tab in the global view, and by setting up a private registry in the advanced options in the cluster-level settings. The global default registry is intended to be used for air-gapped setups, for registries that do not require credentials. The cluster-level private registry is intended to be used in all setups in which the private registry requires credentials.
@@ -35,4 +35,4 @@ You can follow these steps to configure a private registry when you create a clu
**Result:** The new cluster will be able to pull images from the private registry.
The private registry cannot be configured after the cluster is created.
The private registry cannot be configured after the cluster is created.