Skip to content

Commit 481eec3

Browse files
committed
incorporate Anthony's comments
1 parent c5219ff commit 481eec3

File tree

1 file changed

+18
-7
lines changed

1 file changed

+18
-7
lines changed

articles/container-apps/managed-identity-image-pull.md

Lines changed: 18 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,15 @@ Create a container app revision with a private image and the system-assigned man
9393
1. Select **Save**.
9494
1. Select **Create** from the **Create and deploy new revision** page.
9595

96-
A new revision will be created and deployed. The portal will automatically attempt to add the `acrpull` role to the user-assigned managed identity. If the role isn't added, you can add it manually. You can verify that the role was added by checking the identity in the **Identity** pane of the container app page.
96+
A new revision will be created and deployed. The portal will automatically attempt to add the `acrpull` role to the user-assigned managed identity. If the role isn't added, you can add it manually.
97+
98+
You can verify that the role was added by checking the identity from the **Identity** pane of the container app page.
99+
100+
1. Select **Identity** from the left menu.
101+
1. Select the **User assigned** tab.
102+
1. Select the user-assigned managed identity.
103+
1. Select **Azure role assignments** from the menu on the managed identity resource page.
104+
1. Verify that the `acrpull` role is assigned to the user-assigned managed identity.
97105

98106
### Clean up resources
99107

@@ -172,7 +180,14 @@ Edit the container to use the image from your private Azure Container Registry,
172180
1. Select **Create** at the bottom of the **Create and deploy new revision** page
173181
1. After a few minutes, select **Refresh** on the **Revision management** page to see the new revision.
174182

175-
A new revision will be created and deployed. The portal will automatically attempt to add the `acrpull` role to the system-assigned managed identity. If the role isn't added, you can add it manually. You can verify that the role was added by checking the identity in the **Identity** pane of the container app page.
183+
A new revision will be created and deployed. The portal will automatically attempt to add the `acrpull` role to the system-assigned managed identity. If the role isn't added, you can add it manually.
184+
185+
You can verify that the role was added by checking the identity in the **Identity** pane of the container app page.
186+
187+
1. Select **Identity** from the left menu.
188+
1. Select the **System assigned** tab.
189+
1. Select **Azure role assignments**.
190+
1. Verify that the `acrpull` role is assigned to the system-assigned managed identity.
176191

177192
### Clean up resources
178193

@@ -559,9 +574,6 @@ New-AzContainerApp @AppArgs
559574

560575
Update the container app with the image from your private container registry and add a system-assigned identity to authenticate the Azure Container Registry pull. You can also include other settings necessary for your container app, such as ingress, scale and Dapr settings.
561576

562-
If your image tag isn't `latest`, replace 'latest' with your tag.
563-
564-
565577
# [Azure CLI](#tab/azure-cli)
566578

567579
Set the registry server and turn on system-assigned managed identity in the container app.
@@ -571,10 +583,9 @@ az containerapp registry set \
571583
--name $CONTAINERAPP_NAME \
572584
--resource-group $RESOURCE_GROUP \
573585
--identity system \
574-
--server "$REGISTRY_NAME.azurecr.io:latest"
586+
--server "$REGISTRY_NAME.azurecr.io"
575587
```
576588

577-
578589
```azurecli
579590
az containerapp update \
580591
--name $CONTAINERAPP_NAME \

0 commit comments

Comments
 (0)