Container Apps revision-scope change behavior

Chris Jones 1 Reputation point
2023-01-03T18:59:55.257+00:00

I'm running a container app in single-revision mode.
When I push a new version of the container to the repository and run the following command:

az containerapp up ... --image

Azure Container Apps
Azure Container Apps
An Azure service that provides a general-purpose, serverless container platform.
325 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Akram Kathimi 1,046 Reputation points Microsoft Employee
    2023-01-11T09:19:49.7166667+00:00

    Hi @Chris Jones ,

    There is unfortunately no way to force pulling a new image with the same name and tag.

    You can delete and recreate the container group to force pulling the new image, as described here. For clarity I'm quoting the document below:

    When you delete a container group and recreate it, it's not "redeployed," but created new. All image layers are pulled fresh from the registry, not from those cached by a previous deployment. The IP address of the container might also change due to being deployed to a different underlying host.

    I found other suggestions online, but cannot confirm if they work or not, feel free to test them :).

    This is by design to always have the images cached for faster operations and restart times.

    Please "Accept as Answer" if it helped, so that it can help others in the community looking for help on similar topics.

    0 comments No comments