Azure web-app - Multi-container unit was not started successfully for react app

Viral Patel 0

I am using the Azure web app and running the react app using the docker-compose. It used to work but since I upgraded to

React 18.3.1 Nextjs 14.2.3

and it stopped working and gave me this error in the log Azure web app - Multi-container unit was not started successfully. But after 30 mins it starts working and stops occasionally.

ajkuma 24,396 Reputation points Microsoft Employee

2024-07-02T03:13:43.7333333+00:00

Viral Patel, Just checking in to see if you had got a chance to see the previous response. If the answer helped (pointed you in the right direction) > please click Accept Answer Or please share the requested/more info to help you better.

1 answer

ajkuma 24,396 Reputation points Microsoft Employee

2024-07-01T17:08:25.2933333+00:00

Viral Patel, Apologies for the delayed response.

To better assist you on this, could you please let us know what is the exact error message that you receive? What App Service Plan (ASP) are you using?

I understand the issue you mentioned after 30 mins it starts working and stops occasionally.

--Just to isolate the issue, Based on my understanding of your scenario, you may increase the time out by with the WEBSITES_CONTAINER_START_TIME_LIMIT app setting.) (up to a maximum of 1800)

--If you haven't done, to isolate the issue, you may leverage App Service diagnostics from Azure Portal> Navigate to your App Service app in the Azure Portal.

In the left navigation, click on Diagnose and solve problems - Review - “Configuration and Management and “Availability and Performance” (screenshot below)

--Enable and review logs to fetch more details about the error: #enable-application-logging-linuxcontainer and Access log files

Kindly let us know how it goes, I'll follow-up with you further.

If the answer helped (pointed, you in the right direction) > please click Accept Answer - it will help users to find the answers quickly.
Please sign in to rate this answer.
Viral Patel 0 Reputation points

2024-07-03T12:40:30.17+00:00

This is the log that I was able to retrieve.

ajkuma 24,396 Reputation points Microsoft Employee

2024-07-04T05:57:15.4933333+00:00

Viral Patel, thanks for the follow-up.

We would need more info about your docker-compose to further isolate the issue.

Applications with a lot of logic being executed in initialization on restarts, or during “cold start” events, such as if being moved across instances can already introduce long start or restart times.

Adding a startup script into the equation - one that reinstalls packages, rebuilds, compiles, or others - at runtime, which gets executed on each container start - adds even more time. Regardless though, even for small applications, this can cause increased startup times.

If possible, the solution would be to move the logic contained in this, to more appropriate parts of development. Such as into the build itself, or into a post or pre deployment script.

Nodejs on App Service Linux and why to avoid installing packages in startup scripts

--

Use PM2 to serve the production build build folder already built in Oryx deployment process using this startup command pm2 serve /home/site/wwwroot/build --no-daemon --spa this will avoid running React development mode. You can find more details in this reference.

Kindly let us know how it goes, I'll follow-up with you privately further (for additional details for investigation).

ajkuma 24,396 Reputation points Microsoft Employee

2024-07-04T05:57:58.84+00:00

Viral Patel, To provide additional info:

On custom container for Azure App Service, the following Docker Compose configuration options are unsupported.

Azure doc | Configure a custom container for Azure App Service| Unsupported options

build (not allowed)

depends_on (ignored)

networks (ignored)

secrets (ignored)

ports other than 80 and 8080 (ignored)

default environment variables like $variable and ${variable} unlike in docker

Viral Patel 0 Reputation points

2024-07-04T13:57:08.5766667+00:00

version: "3"

services:

frontend:

image: "imagename:tag"

ports:

- "3000:3000"

restart: always

Above is the simple compose file I used previously and the issue started when we upgraded the Nextjs version. I have also tried with ports 80 & 8080 but it still gives the same problem.

Another thing that we tried is running the app via the "Single Container" option and it works.
Sign in to comment

Share via

Azure web-app - Multi-container unit was not started successfully for react app

1 answer