Skip to content

Commit fb6af77

Browse files
authored
Update articles/deployment-environments/how-to-configure-extensibility-bicep-container-image.md
1 parent 756719c commit fb6af77

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

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

237237
### Push the Docker image to a registry
238238

239-
In order to use custom images, you need to store them in a registry like Azure Container Registry (ACR) or Docker Hub.
239+
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.
240240

241241
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.
242242

0 commit comments

Comments
 (0)