Skip to content

Commit 2803108

Browse files
Merge pull request #268008 from tejaswikolli-web/publicmanage
Public manage
2 parents 608f575 + 7652c4e commit 2803108

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

articles/container-registry/buffer-gate-public-content.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,12 @@ For details, see [Docker Hub authenticated pulls on App Service](https://azure.g
6060
* **Image registry password**: \<Docker Hub token>
6161
* **Image**: docker.io/\<repo name\>:\<tag>
6262

63+
64+
## Configure Artifact Cache to consume public content
65+
66+
The best practice for consuming public content is to combine registry authentication and the Artifact Cache feature. You can use Artifact Cache to cache your container artifacts into your Azure Container Registry even in private networks. Using Artifact Cache not only protects you from registry rate limits, but dramatically increases pull reliability when combined with Geo-replicated ACR to pull artifacts from whichever region is closest to your Azure resource. In addition, you can also use all the security features ACR has to offer, including private networks, firewall configuration, Service Principals, and more. For complete information on using public content with ACR Artifact Cache, check out the [Artifact Cache](/azure/container-registry/tutorial-artifact-cache.md) tutorial.
67+
68+
6369
## Import images to an Azure container registry
6470

6571
To begin managing copies of public images, you can create an Azure container registry if you don't already have one. Create a registry using the [Azure CLI](container-registry-get-started-azure-cli.md), [Azure portal](container-registry-get-started-portal.md), [Azure PowerShell](container-registry-get-started-powershell.md), or other tools.

0 commit comments

Comments
 (0)