App container failed to start: Container for site has exited, failing site start

Question

App container failed to start: Container for site has exited, failing site start

Meesala, Bhagya Harika 0

I'm trying to start/restart the App service from Azure portal, but the URL shows Application Error

Upon diagnostics, it looks like the container is failing site start.

User's image

SnehaAgrawal-MSFT 22,701 Reputation points Moderator

2024-06-10T12:13:56.5766667+00:00

@Meesala, Bhagya Harika Thanks for asking question!

could not open shared object file: no such file or directory

This will happen when a python dependency you are using requires a library not installed on app services python images.

The workaround for this would be to create an app service startup script to install these libraries.

Refer- Python Deployment could not open shared object file: no such file or directory

Also check this link on Things you should for Web App and Linux-

https://techcommunity.microsoft.com/t5/apps-on-azure-blog/things-you-should-know-web-apps-and-linux/ba-p/392472#NoPing

Hope this help.

Let us know.
Meesala, Bhagya Harika 0 Reputation points

2024-06-11T16:27:33.1233333+00:00

Thanks @snehaagarwal0608 for your response. I have created the startup.sh script to install the required libraries.

But below is the error I see once I add that script file saying

ModuleNotFoundError: No Module named 'app'

But I confirm that my application name app.py
Lex Li (Microsoft) 6,032 Reputation points Microsoft Employee

2024-10-04T22:04:31.1466667+00:00

Since app.py is in ~/site/repository directory, while startup.sh is in ~, the module resolution can fail if the working directory wasn't set properly. Would you mind edit the question to include your latest version of startup.sh? That might allow others to suggest what changes are needed.

2 answers

Your answer

SnehaAgrawal-MSFT 22,701 Reputation points Moderator

2024-06-10T12:13:56.5766667+00:00

@Meesala, Bhagya Harika Thanks for asking question!

could not open shared object file: no such file or directory

This will happen when a python dependency you are using requires a library not installed on app services python images.

The workaround for this would be to create an app service startup script to install these libraries.

Refer- Python Deployment could not open shared object file: no such file or directory

Also check this link on Things you should for Web App and Linux-

https://techcommunity.microsoft.com/t5/apps-on-azure-blog/things-you-should-know-web-apps-and-linux/ba-p/392472#NoPing

Hope this help.

Let us know.
Meesala, Bhagya Harika 0 Reputation points

2024-06-11T16:27:33.1233333+00:00

Thanks @snehaagarwal0608 for your response. I have created the startup.sh script to install the required libraries.

But below is the error I see once I add that script file saying

ModuleNotFoundError: No Module named 'app'

But I confirm that my application name app.py
Lex Li (Microsoft) 6,032 Reputation points Microsoft Employee

2024-10-04T22:04:31.1466667+00:00

Since app.py is in ~/site/repository directory, while startup.sh is in ~, the module resolution can fail if the working directory wasn't set properly. Would you mind edit the question to include your latest version of startup.sh? That might allow others to suggest what changes are needed.

Answer 1

Laziz 190 Microsoft Employee

Hi Meesala, Bhagya Harika,

For the latest error you got on "ModuleNotFoundError: No module named 'app'", will you please try the following:

In your Web App, click Deployment -> Deployment Center, then open Logs section to see if there were any deployment failures (very likely, yes).
After that, click Sync button as shown below, wait for its completion and verify that the latest status is Success (Active). If yes, please restart the Web App and test it again. Hopefully, it will resolve the issue.

User's image

Answer 2

@Meesala, Bhagya Harika Thanks for reply!

ModuleNotFoundError will usually present itself where the module/package you’re importing is missing. Either it was never defined in requirements.txt, deployment was done but package installation was never done to produce site-packages, or the library is there and the package installation was done - but it’s dependent on a native library (.so files) that is not available in the container.

Ultimately, this will always cause the application/container to crash.

Suggest you refer the detailed steps mentioned in the link- https://azureossd.github.io/2022/11/24/Python-on-Linux-App-Service-and-ModuleNotFound-Errors/

Share via

App container failed to start: Container for site has exited, failing site start

2 answers

Your answer