Azure Container Instance was terminated by Service Fabric with Exit Code 7147, won't start, stuck in Pending state

Octavian Cismasu 21 Reputation points
2024-02-23T15:33:30.4366667+00:00

A few of my Container Instances were shut down at 4am today by Service Fabric, with exit code 7147. image

Subsequent attempts to restart the container are failing even 6 hours (!) after the initial shutdown event. The container status remains in "Pending" or "Repairing" state, with no apparent way to resolve the situation. I fully understand that this situation may occur periodically for maintenance or load-balancing on Azure. However, why do container instances take so long to start again? What does Microsoft provide as solution or tools to further investigate this issue and to speed up the recovery of Container Instances availability after such events? Thank you.

Azure Service Fabric
Azure Service Fabric
An Azure service that is used to develop microservices and orchestrate containers on Windows and Linux.
267 questions
Azure Container Instances
Azure Container Instances
An Azure service that provides customers with a serverless container experience.
711 questions
{count} votes

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.