Skip to content

Commit 6bff650

Browse files
committed
Minor doc updates
1 parent a421422 commit 6bff650

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/container-instances/using-azure-container-registry-mi.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.custom: mvc, devx-track-azurecli
1414

1515
[Azure Container Registry][acr-overview] (ACR) is an Azure-based, managed container registry service used to store private Docker container images. This article describes how to pull container images stored in an Azure container registry when deploying to container groups with Azure Container Instances. One way to configure registry access is to create an Azure Active Directory managed identity.
1616

17-
Managed identity can also be used to deploy an Azure Container instance or group in a virtual network and authenticate with an Azure Container Registry (ACR) instance that runs behind a private endpoint.
17+
Managed identity can also be used to deploy an Azure Container instance or group in a virtual network and authenticate with an Azure Container Registry (ACR) that runs behind a private endpoint.
1818

1919
## Prerequisites
2020

@@ -166,17 +166,17 @@ az container create --name my-containergroup --resource-group myResourceGroup --
166166

167167
## Deploy in a virtual network using the Azure CLI
168168

169-
To deploy a container group in a vnet using managed identity to authenticate image pulls from an ACR that runs behind a private endpoint via the Azure CLI, use the following command:
169+
To deploy a container group to a virtual network using managed identity to authenticate image pulls from an ACR that runs behind a private endpoint via the Azure CLI, use the following command:
170170

171171
```azurecli-interactive
172-
az container create --name my-containergroup --resource-group myResourceGroup --image <loginServer>/hello-world:v1 --acr-identity $userID --assign-identity $userID --vnet "/subscriptions/$SUBSCRIPTION_ID/resourceGroups/"/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx/resourceGroups/myVnetResourceGroup/providers/ --subnet mySubnetName
172+
az container create --name my-containergroup --resource-group myResourceGroup --image <loginServer>/hello-world:v1 --acr-identity $userID --assign-identity $userID --vnet "/subscriptions/$SUBSCRIPTION_ID/resourceGroups/"/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx/resourceGroups/myVNetResourceGroup/providers/ --subnet mySubnetName
173173
```
174174

175175
For more info on how to deploy to a virtual network see [Deploy container instances into an Azure virtual network](./container-instances-vnet.md).
176176

177177
## Deploy a multi-container group in a virtual network using YAML and the Azure CLI
178178

179-
To deploy a multi-container group in a vnet using managed identity to authenticate image pulls from an ACR that runs behind a private endpoint via the Azure CLI, you can specify the container group configuration in a YAML file. Then pass the YAML file as a parameter to the command.
179+
To deploy a multi-container group to a virtual network using managed identity to authenticate image pulls from an ACR that runs behind a private endpoint via the Azure CLI, you can specify the container group configuration in a YAML file. Then pass the YAML file as a parameter to the command.
180180

181181
```yaml
182182
apiVersion: '2021-10-01'
@@ -193,7 +193,7 @@ properties:
193193
- server: myacr.azurecr.io
194194
identity: '/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx/resourcegroups/myResourceGroup/providers/Microsoft.ManagedIdentity/userAssignedIdentities/myACRId'
195195
subnetIds:
196-
- id: '/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx/resourceGroups/myVnetResourceGroup/providers/Microsoft.Network/virtualNetworks/myVnetName/subnets/mySubnetName'
196+
- id: '/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx/resourceGroups/myVNetResourceGroup/providers/Microsoft.Network/virtualNetworks/myVNetName/subnets/mySubnetName'
197197
name: mySubnetName
198198
containers:
199199
- name: myContainer-1

0 commit comments

Comments
 (0)