You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/vendor/packaging-public-images.mdx
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,14 +8,15 @@ For more information about the Replicated proxy registry, see [About the Replica
8
8
9
9
You can use the Replicated proxy registry to pull both public and private images. Using the Replicated proxy registry for public images can simplify network access requirements for your customers, as they only need to whitelist a single domain (either `proxy.replicated.com` or your custom domain) instead of multiple registry domains.
10
10
11
-
For public images, you can use anonymous access without configuring registry credentials.
11
+
For public images, you need to first configure registry credentials.
12
12
13
13
To pull public images through the Replicated proxy registry, use the following `docker` command:
*`APPSLUG` is your Replicated app slug found on the [app settings page](https://vendor.replicated.com/settings).
19
20
*`REPLICATED_PROXY_DOMAIN` is `proxy.replicated.com` or your custom domain. For information about how to set a custom domain for the proxy registry, see [Using Custom Domains](/vendor/custom-domains-using).
20
21
*`UPSTREAM_REGISTRY_HOSTNAME` is the hostname for the public registry where the image is located. If the image is located in a namespace within the registry, include the namespace after the hostname. For example, `quay.io/namespace`.
21
22
*`IMAGE` is the image name.
@@ -31,28 +32,28 @@ The following examples show how to pull public images from DockerHub:
31
32
32
33
```bash
33
34
# DockerHub is the default when no hostname is specified
0 commit comments