Skip to content

Commit fa7ed42

Browse files
authored
Update articles/deployment-environments/how-to-configure-extensibility-terraform-container-image.md
1 parent f0063fe commit fa7ed42

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/deployment-environments/how-to-configure-extensibility-terraform-container-image.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -182,7 +182,7 @@ docker build . -t {YOUR_REGISTRY}.azurecr.io/customImage:1.0.0
182182

183183
In order to use custom images, you need to store them in a container registry. Azure Container Instances (ACR) is highly recommended for that. Due to its tight integration with ADE, the image can be published without allowing public anonymous pull access.
184184

185-
To use a custom image stored in a public registry, you need to enable anonymous image pull. This way, Azure Deployment Environments can access your custom image to execute in our container.
185+
It's also possible to store the image in a different container registry such as Docker Hub, but in that case it needs to be publicly accessible.
186186

187187
> [!Caution]
188188
> Enabling anonymous (unauthenticated) pull access makes all registry content publicly available for read (pull) actions.

0 commit comments

Comments
 (0)