ACA Container failed despite Exit Code 0?

Nikola Kretschmer 40 Reputation points
2024-01-23T11:10:54.12+00:00

Hi, I'm using Azure Container Apps, just testing one-time running containers. While they work and the output in the logs is as expected, ACA keeps restarting the container and shows it as "Running (at max)" before moving it to "Failed" despite every container run ending with an exit code of 0 (indicating successful completition of the task) I have ingress and all health probes disabled. Scale is 0-1 User's imageUser's image

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

Accepted answer
  1. Anthony Chu - MSFT 861 Reputation points Microsoft Employee
    2024-01-23T15:35:14.9733333+00:00

    Azure Container Apps are for running containers that don’t exit. It will restart your container if it exits for any reason. For run-to-completion scenarios where the container exits when it finishes its work, you can use the jobs feature in Azure Container Apps. Learn more here https://learn.microsoft.com/en-us/azure/container-apps/jobs?tabs=azure-cli#compare-container-apps-and-jobs

    0 comments No comments

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.