Timeouts when pulling large Windows container images to launch as an Azure Container Instance

Jean Lord 20 Reputation points
2023-06-07T21:40:03.9766667+00:00

We are using Azure Container Instances to launch rather large Windows container images. These often timeout after roughly 7 minutes with the following error:

"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Canceled'."

We have tried the "premium" tier for Azure Container Registry but continue to encounter these timeouts.

We don't have much room for optimizing the size of these images and are hoping someone can suggest a way to increase the timeout limit. They launch once in while but the majority of the time we encounter this 7 minute timeout threshold.

Azure Container Registry
Azure Container Registry
An Azure service that provides a registry of Docker and Open Container Initiative images.
511 questions
Azure Container Instances
Azure Container Instances
An Azure service that provides customers with a serverless container experience.
758 questions
{count} votes

Accepted answer
  1. Akram Kathimi 1,371 Reputation points Microsoft Employee
    2023-06-08T06:48:03.69+00:00

    Hi @Jean Lord ,

    Thank you for your question.

    Please note that increasing the timeout is not possible.

    If reducing the image size is not possible, I would suggest checking the list of precached images in Azure Container Images, available via the List Cached Images API. You might be able to switch out an image layer for one of the precached images.

    Please check the FAQ page for more information.

    Thank you.

    Please Accept the answer if the information helped you. This will help us and others in the community as well.


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.