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-private-images.md
+48Lines changed: 48 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -249,6 +249,54 @@ For example:
249
249
replicated registry test index.docker.io --image my-company/my-image:v1.2.3
250
250
```
251
251
252
+
## Pull public images through the Replicated proxy registry
253
+
254
+
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 (`proxy.replicated.com` or your custom domain) instead of multiple registry domains.
255
+
256
+
For public images, you can use anonymous access without configuring registry credentials. The URL structure for pulling public images is:
For private registries or when you need to use specific credentials for quasi-public registries, configure the registry as an external registry first and use `/proxy/` instead of `/anonymous/` in the URL path.
298
+
:::
299
+
252
300
## Related Topic
253
301
254
302
[Tutorial: Using ECR for Private Images](tutorial-ecr-private-images)
0 commit comments