Are there any best practices on continuous deployment to an Azure Container Instance so that it keeps the public IP? Or mapping an Azure Reserved IP to a dynamic IP that the ACI gets bound to at deployment?
相关问题
- running headless chrome in an microsoft azure web
- Docker task in Azure devops won't accept "$(pw
- Register MicroServices in Azure Active Directory (
- Removing VHD's from Azure Resource Manager aft
- Cannot use the Knowledge academic API
相关文章
- SQL Azure Reset autoincrement
- How to cast Azure DocumentDB Document class to my
- Can't get azure web role to run locally using
- Azure WebApp - Unable to auto-detect the runtime s
- How to change region for Azure WebSite
- Azure webjob vs cloud service
- Azure data transfer Identity Column Seed Jumped by
- Download Azure web app?
Currently, your best bet is to create a DNS A record for the app and remap it to the new IP when you create a new container. However, we are working on enabling you to simply update the container and keep the IP.
Update: You can now request a DNS entry for your ACI container in the Microsoft-managed azurecontainer.io domain using the
dns-name-label
switch in the az cli. You can keep this DNS stable across updates.az container create -n helloworld --image microsoft/aci-helloworld -g myResourceGroup --dns-name-label mycontainer