5 containers not fully started within one container group, but it's working when putting the 5th container in 2nd group

Question

5 containers not fully started within one container group, but it's working when putting the 5th container in 2nd group

Allen Han 1

I have an application that consists of 5 docker images. When creating all 5 containers in one group, it never succeed. It would time out. However, if I put the 5th container in the 2nd container group, it worked. Any ideas about the issue?

The 5th container is a frontend app running with nginx. It's quite small. The other containers included mongo, activemq, vault, and a springboot service.

Monalla-MSFT 13,166 Reputation points Moderator

2023-09-13T13:12:28.36+00:00

@Allen Han - Just checking in to see if the below answer helped. If this answers your query, do click "Accept as Answer" and click "Yes" for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.

1 answer

Your answer

Monalla-MSFT 13,166 Reputation points Moderator

2023-09-13T13:12:28.36+00:00

@Allen Han - Just checking in to see if the below answer helped. If this answers your query, do click "Accept as Answer" and click "Yes" for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.

Answer 1

Eddie Neto 1,256

Hi @Allen Han

Thanks for reaching Microsoft Q&A.

Are you setting up the limits and requests for each container? If not, please configure and test again.

Do you have any logs to be shared?

https://learn.microsoft.com/en-us/azure/container-instances/container-instances-container-groups#resource-allocation

Also please only share here the Resource Group name and Name of ACI.

Allen Han 1 Reputation point

2023-08-10T14:36:35.3933333+00:00

Hi @Eddie Neto ,

Thanks for checking the issue, and the suggestions. I was using terraform to create the resources. I put CPU and memory attributes for each container definition.

When I first time created a container group with 5 containers, I got the following error when running terraform apply:

Resource Group Name: "Handshake-Demo-n7c7ngam"

│ Container Group Name: "acigroup-n7c7ngam"): performing ContainerGroupsCreateOrUpdate: containerinstance.ContainerInstanceClient#ContainerGroupsCreateOrUpdate: Failure sending request: StatusCode=0 -- Original Error: Code="InternalServerError" Message="Encountered an internal server error. The tracking activity id is '2871b481-40ce-44c9-9e43-88b055fbabc4', correlation id is 'b1ebbf11-df64-39e2-611a-24dcf4d3f8f4'."

│

│ with azurerm_container_group.handshake,

│ on c7-container_group.tf line 1, in resource "azurerm_container_group" "handshake":

│ 1: resource "azurerm_container_group" "handshake" {

With this error, the container group was not created. Here is the info:

Resource Group: "Handshake-Demo-n7c7ngam" Container Group: acigroup-n7c7ngam

Is it possible to get further information with the activity id shown above?

From my early tests, when 4 containers were created first, then the container group and all containers were created properly. When I added the 5th container, it never returned from the call, and eveutally timed out. There was no logs avaiable then.

Thanks
Eddie Neto 1,256 Reputation points

2023-08-11T14:06:55.79+00:00

Hi @Allen Han

I cannot see anything with this Resource Group: "Handshake-Demo-n7c7ngam" Container Group: acigroup-n7c7ngam....Have you deleted? If yes, can you deploy a new one and just leave it running/stopped/restating status.
Eddie Neto 1,256 Reputation points

2023-08-11T14:21:11.21+00:00

@Allen Han

Are you also creating container using VNET? If yes, what's the subnet range you are using?
Allen Han 1 Reputation point

2023-08-11T21:53:04.5333333+00:00

Hi @Eddie Neto ,

Sorry about the confusion. With the error happened during the container group creation from my last comment, the container group was not created at all. I thought it could be the side-effect of the issue of not able to create 5 containers, so I kept it that way in hope it could provide pertinent information for investigation.

However, when I tried to create 4 containers or even just one container, I got similar error. Looks to me a different issue happened, it even occurred when I created a totally new resource group.

Please give me some time to check it, I will let you know when I can create the case with the original issue happening.

Thanks
Allen Han 1 Reputation point

2023-08-11T21:57:56.8133333+00:00

removed due to duplication
Eddie Neto 1,256 Reputation points

2023-09-04T07:44:24.4733333+00:00

Hi @Allen Han

Hope you good! Just want to confirm if we have the issue mitigated, since I don't see any update from your side.

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

Share via

5 containers not fully started within one container group, but it's working when putting the 5th container in 2nd group

1 answer

Your answer