Allow an ACI container to update itself when the image is updated
This scenario is currently not supported and an update requires the container to be deleted (which forces an IP. Address change)
ACI currently supports in-place updates by submitting a create request on an existing resource. Is this sufficient for you or are you hoping to have automatic updates by detecting when a new push to “latest” occurs?
Yaroslav Admin commented
Having a CLI command/API to patch the container instance (i.e. preserve all existing configurations and only change those specified in the update command) would be very useful. The approach described in the documentation is not very convenient as it requires to pass a complete container configuration: environment variables, ports, DNS label, etc.
Similar to how it is possible for Azure WebApp:
az webapp config container set \
--docker-custom-image-name my-image:my-version \
--name my-webapp \
Our use case is to deploy a new version of a service automatically every time new Docker image is built. We have a big ARM template which deploys whole resource group and configures all services, but it is convenient to be able to change an image version without re-deploying whole resource group.
I would love to see the ability to deploy on docker hub webhook, or integration with github actions/azure devops pipelines. I would also love being able to update the container image without having to maintain the entire state of the container in the command.
When I use az container create to update only container image it removes all other settings from container (dns, env variables and so on). This is not useful when I want just to update the image and leave all other settings as is. Add some flag or something to say the CLI leave the settings untouched in case changes not present.
Thanks for this feedback! The current documentation explaining the in-place update flow is here with details:
We will be supporting CLI cmds to make patch updates as well for properties that support patching. We are also exploring eventgrid integration, please leave your feedback on that suggestion if you find it useful.
Would be great to get automatic upgrades on image updated.
Have automatic updates by detecting when a new push to “latest” occurs.
Luis Delgado commented
In the past one had to delete the instance and redeploy, which led to a change in public IP.
As long as the IP and General configuration is preserved when using an existing ACI , that is sufficient for me
Sebastian Godelet commented
> ACI currently supports in-place updates by submitting a create request on an existing resource
It would be nice if this is documented better, and esp. what happens to the public IP if the container is re-deployed this way (stays, changes)?
Artem Polikarpov commented
Yes, it would be great to have automatic updates like it is already done for deploy (image) in web application, so that all deployment/update could be done from Azure portal menus/buttons. Then there will be 'less room for an error'.
Mitchell Barry commented
Even the ability to re-deploy ARM template with the same image:tag, it would be nice to have the image re-pulled and started in the Azure Container Group.