I am unable to stop my app

Question

I am unable to stop my app

Marcus 20

I have attached a screenshot. I get an error shown in the attachment. Please help ASAP as it is consuming resources. Screenshot 2025-04-06 170410.png

Marten Theunissen 676 Reputation points

2025-04-06T07:45:40.0066667+00:00

Good day,

Thanks for your question. Please remember to mark this answer.

It sounds like you're having trouble stopping a container app. Here are some steps you can follow to stop an Azure Container App:

Using Azure CLI:

You can deactivate a revision to shut down the containers. If you deactivate all active revisions, you will effectively stop your container app. Use the following commands:

az containerapp revision deactivate --resource-group <your-resource-group> --name <your-container-app-name> --revision <revision-name>

To stop the container app using the REST API, you can use the following command:

az rest -m POST -u "/subscriptions/<your-subscription-id>/resourceGroups/<your-resource-group>/providers/Microsoft.App/containerapps/<your-container-app-name>/stop?api-version=2023-04-01-preview"

Using Azure Portal:

Unfortunately, as of now, stopping a container app directly from the Azure Portal is not supported. You will need to use the CLI or REST API methods mentioned above12.

Using Logic Apps:

You can also use Azure Logic Apps to start and stop container apps programmatically. This involves setting up a Logic App with a connector to make calls to the Azure REST API3.
Marcus 20 Reputation points

2025-04-06T09:39:43.1+00:00

when will azure portal be working again for stopping container apps. it's been working all along until now.
Marcus 20 Reputation points

2025-04-06T09:43:16.61+00:00

I ran the command and the revisions shows as degraded but the container app still shows as start and not stop.
Marcus 20 Reputation points

2025-04-06T09:43:51.6133333+00:00

and when i try and top it it still produces the same error as in my previous attachment.
Marten Theunissen 676 Reputation points

2025-04-06T09:57:52.3366667+00:00

Please share the log, blank out sensitive information. I want to ensure it not getting stuck trying to call the 100.100..230.54 that is not timing out, confirm under your app setting the details are correct
Marcus 20 Reputation points

2025-04-06T10:46:20.0366667+00:00

Which log. Please provide exact instructions. Thanks.
Sai Prabhu Naveen Parimi 1,150 Reputation points Microsoft External Staff

2025-04-07T08:03:40.11+00:00

@Marten Theunissen Could you please review the Marcus comment
Marten Theunissen 676 Reputation points

2025-04-07T08:15:32.0266667+00:00

Good day Marcus,IF you have not enabled any logging it might be of great insight if you are not viewing the life logging. Please have a look at the service for logging below.

Azure Container Apps generates system logs to inform you about the status of service-level events. The log messages include the following information:

Successfully created dapr component

Successfully updated dapr component

Error creating dapr component

Successfully mounted volume

Error mounting volume

Successfully bound Domain

Auth enabled on app

Creating authentication config

Auth config created successfully

Setting a traffic weight

Creating a new revision:

Successfully provisioned revision

Deactivating Old revisions

Error provisioning revision

https://learn.microsoft.com/en-us/azure/container-apps/logging
Marcus 20 Reputation points

2025-04-08T05:16:11.3566667+00:00

I am extremely unhappy with Microsoft support and didn't realise that it would take so long and still as simple thing like stopping the container app could not be resolved. The revision is deactivated but the container WILL NOT STOP. I don't have the knowledge to do some of the things you mentioned and it seems paying for Microsopft support is a waste of money since the change in support process recently.
Sai Prabhu Naveen Parimi 1,150 Reputation points Microsoft External Staff

2025-04-08T08:49:14.76+00:00

@Marcus

I have sent you a private message. Could you please check and respond so that we can connect further to troubleshoot the issue

1 answer

Your answer

Marten Theunissen 676 Reputation points

2025-04-06T07:45:40.0066667+00:00

Good day,

Thanks for your question. Please remember to mark this answer.

It sounds like you're having trouble stopping a container app. Here are some steps you can follow to stop an Azure Container App:

Using Azure CLI:

You can deactivate a revision to shut down the containers. If you deactivate all active revisions, you will effectively stop your container app. Use the following commands:

az containerapp revision deactivate --resource-group <your-resource-group> --name <your-container-app-name> --revision <revision-name>

To stop the container app using the REST API, you can use the following command:

az rest -m POST -u "/subscriptions/<your-subscription-id>/resourceGroups/<your-resource-group>/providers/Microsoft.App/containerapps/<your-container-app-name>/stop?api-version=2023-04-01-preview"

Using Azure Portal:

Unfortunately, as of now, stopping a container app directly from the Azure Portal is not supported. You will need to use the CLI or REST API methods mentioned above12.

Using Logic Apps:

You can also use Azure Logic Apps to start and stop container apps programmatically. This involves setting up a Logic App with a connector to make calls to the Azure REST API3.
Marcus 20 Reputation points

2025-04-06T09:39:43.1+00:00

when will azure portal be working again for stopping container apps. it's been working all along until now.
Marcus 20 Reputation points

2025-04-06T09:43:16.61+00:00

I ran the command and the revisions shows as degraded but the container app still shows as start and not stop.
Marcus 20 Reputation points

2025-04-06T09:43:51.6133333+00:00

and when i try and top it it still produces the same error as in my previous attachment.
Marten Theunissen 676 Reputation points

2025-04-06T09:57:52.3366667+00:00

Please share the log, blank out sensitive information. I want to ensure it not getting stuck trying to call the 100.100..230.54 that is not timing out, confirm under your app setting the details are correct
Marcus 20 Reputation points

2025-04-06T10:46:20.0366667+00:00

Which log. Please provide exact instructions. Thanks.
Sai Prabhu Naveen Parimi 1,150 Reputation points Microsoft External Staff

2025-04-07T08:03:40.11+00:00

@Marten Theunissen Could you please review the Marcus comment
Marten Theunissen 676 Reputation points

2025-04-07T08:15:32.0266667+00:00

Good day Marcus,IF you have not enabled any logging it might be of great insight if you are not viewing the life logging. Please have a look at the service for logging below.

Azure Container Apps generates system logs to inform you about the status of service-level events. The log messages include the following information:

Successfully created dapr component

Successfully updated dapr component

Error creating dapr component

Successfully mounted volume

Error mounting volume

Successfully bound Domain

Auth enabled on app

Creating authentication config

Auth config created successfully

Setting a traffic weight

Creating a new revision:

Successfully provisioned revision

Deactivating Old revisions

Error provisioning revision

https://learn.microsoft.com/en-us/azure/container-apps/logging
Marcus 20 Reputation points

2025-04-08T05:16:11.3566667+00:00

I am extremely unhappy with Microsoft support and didn't realise that it would take so long and still as simple thing like stopping the container app could not be resolved. The revision is deactivated but the container WILL NOT STOP. I don't have the knowledge to do some of the things you mentioned and it seems paying for Microsopft support is a waste of money since the change in support process recently.
Sai Prabhu Naveen Parimi 1,150 Reputation points Microsoft External Staff

2025-04-08T08:49:14.76+00:00

@Marcus

I have sent you a private message. Could you please check and respond so that we can connect further to troubleshoot the issue

Answer 1

@Marcus Thanks for your patience on this. I am summarizing the same and posting as answer for the benefit of other community members.

I have reached out to container app engineering team and sharing the below.

Team has suggested to delete and re-deploy the container app without using --source option in az cli.

As you are using deploy artifact(preview) which is SourceToCloud (s2c) and it is set for deprecation.
Team has highly recommended to adopt any of the below deployment method to deploy your container app.

Docker file build using docker build locally or docker GitHub action.
ACR build task: Tutorial - Quick Docker Image Build with Azure ACR Tasks - Azure Container Registry | Microsoft Learn

For ASA(Azure Springs) to container apps migration, team are working on new deployment mechanism to perform jar file deployment without managing the runtime image and we don't have any ETA at this moment.

Hope this helps, let me know you have any further questions on this.

Please accept as Yes if the answer is helpful so that it can help others in the community.

Share via

I am unable to stop my app

1 answer

Your answer