Skip to content

Commit 1bbbff4

Browse files
Merge pull request #220540 from madsd/xenonvnet
Xenonvnet
2 parents 9507c4d + 33cc08c commit 1bbbff4

File tree

1 file changed

+3
-7
lines changed

1 file changed

+3
-7
lines changed

articles/app-service/configure-custom-container.md

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -114,18 +114,14 @@ Use the following steps to configure your web app to pull from ACR using managed
114114
115115
You are all set, and the web app will now use managed identity to pull from Azure Container Registry.
116116
117-
::: zone pivot="container-linux"
118-
119117
## Use an image from a network protected registry
120118
121-
To connect and pull from a registry inside a virtual network or on-premises, your app will need to be connected to a virtual network using the VNet integration feature. This is also need for Azure Container Registry with private endpoint. When your network and DNS resolution is configured, you enable the routing of the image pull through the VNet by setting the App Setting `WEBSITE_PULL_IMAGE_OVER_VNET=true`:
119+
To connect and pull from a registry inside a virtual network or on-premises, your app will need to be connected to a virtual network using the virtual network integration feature. This is also needed for Azure Container Registry with private endpoint. When your network and DNS resolution is configured, you enable the routing of the image pull through the virtual network by configuring the `vnetImagePullEnabled` site setting:
122120
123121
```azurecli-interactive
124-
az webapp config appsettings set --resource-group <group-name> --name <app-name> --settings WEBSITE_PULL_IMAGE_OVER_VNET=true
122+
az resource update --resource-group <group-name> --name <app-name> --resource-type "Microsoft.Web/sites" --set properties.vnetImagePullEnabled [true|false]
125123
```
126124

127-
::: zone-end
128-
129125
## I don't see the updated container
130126

131127
If you change your Docker container settings to point to a new container, it may take a few minutes before the app serves HTTP requests from the new container. While the new container is being pulled and started, App Service continues to serve requests from the old container. Only when the new container is started and ready to receive requests does App Service start sending requests to it.
@@ -477,7 +473,7 @@ Multi-container is currently in preview. The following App Service platform feat
477473
- Authentication / Authorization
478474
- Managed Identities
479475
- CORS
480-
- VNET integration is not supported for Docker Compose scenarios
476+
- Virtual network integration is not supported for Docker Compose scenarios
481477
- Docker Compose on Azure App Services currently has a limit of 4,000 characters at this time.
482478
483479
### Docker Compose options

0 commit comments

Comments
 (0)