Scherlac
commented
7 months ago Recently we had in one of our app service the same error message even with single container.
The strange part was that it worked for two years flawless, we did not change intentionally anything.
Initial symptoms:
The application returns 5xx http error code
On the Deployment center / Logs page we only get the following message: "Failed to load container logs: Resource containerlog of type text not found"
Recover attempts: I tried start/stop the application, scale up/down the service plan, select basic/premium sku. even with stock nginx container image the app service does not provide logs.
What we observed: The application returns 5xx http error code The Development Tools / Advanced Tools returns an error page: ":( Application Error If you are the application administrator, you can access the " The Development Tools / SSH return an error page: ":( Application Error If you are the application administrator, you can access the "
Resolution:
Later, using the Container Issues Tools from Diagnose and solve problems section showed the following error:
[BYOS] Custom storage volume(s) failed to initialize: [/var/LWASFiles/Sites/xxxx-d-we-001/f60654]
It turnet out, that the related storage account was recreated.
I would like to deploy a web app with a docker-compose. My images are stored in a private registry in a private vnet. My web app is deploy in a private vnet. The only log I have is : 'Failed to load container logs: Resource containerlog of type text not found' If I try to deploy the same image with container type 'single container' I have no issue.
I asked the Azure support they told me "The docker compose is not supported with regional Vnet integration" and to open a github issue here.
Thank you.