Failed to load container logs: Resource containerlog of type text not found

Question

Failed to load container logs: Resource containerlog of type text not found

Ken Fly 46

Previously I can access to application logs from logs tab of App service, Deployment Center

After last deployment, it suddenly only shows Failed to load container logs: Resource containerlog of type text not found from Deployment Center's Logs tab

I don't know what happened.

But I can still access to logs from Monitoring's Log stream.

So strange.

However, I have some app services with Log stream grayed out. Does anyone know why?

~~~~update~~~~

One of my app services, yesterday and this morning, it still shows Failed to load container logs: Resource container log of type text not found from Deployment Center's Logs tab
This afternoon, it suddenly work back to normal and show logs in Deployment Center's Logs tab. I absolutely did nothing to it.

But most of my app services, still show Failed to load container logs: Resource containerlog of type text not found

MayankBargali-MSFT 70,936 Reputation points Moderator

2022-10-26T06:12:01.077+00:00

@Ken Fly Thanks for reaching out. Can you please confirm the resource for which you are observing this behavior? Is this azure webapss or azure container apps so the right tags can be added to assist you further.
Gary Anderson 1 Reputation point

2022-10-28T07:35:29.07+00:00

This has been happening to me for about a month now - first on my production app service instance, but now also in my test instance.

I do not believe this is related to any configuration change we have deliberately made as we haven't changed our build or dockerfile for a long time (it's also happening to @Ken Fly so that would be a big coincidence that we both made the same change) and it also probably isn't related to the base docker image as it happened to our live build long before our test build even though they are both built on the same base (mcr.microsoft.com/dotnet/aspnet:6.0).

@MayankBargali-MSFT for me this is happening on my Azure App Service which is Linux Premium V2 and is running a docker container. We witness the same lack of logs, with the "Failed to load container logs: Resource containerlog of type text not found" error message, in both the staging and production slots, when we go to Deployment Center > Logs.

Please feel free to reach out to me for full details of the subscription and instance this is happening to, to aid your investigations. I would have raised it before with Azure Support but we don't have paid support and I couldn't be bothered with the rigmarole of getting a one-time pass from support on Twitter!

In terms of severity, this is really just an inconvenience. Once we deploy a new container I like to jump to the logs tab to check it has fully pulled and started up before switching staging <-> production - as KenFly says we can just jump to Log Stream instead.
MayankBargali-MSFT 70,936 Reputation points Moderator

2022-10-31T07:49:08.093+00:00

@Gary Anderson Thanks for the details. I have added the azure-webapps tag so the team can review it and assist you further.
Ken Fly 46 Reputation points

2022-11-07T00:12:08.433+00:00

sorry for later response. It is azure web application, not container apps
khoai.nguyen 0 Reputation points

2023-06-26T07:16:13.73+00:00

@MayankBargali-MSFT I have the same question in Korea Central with App Service Plan container/I1v2 Docker compose multi container.

I used this article but it is not work. https://learn.microsoft.com/en-us/azure/app-service/tutorial-multi-container-app

Please let me know when it is fixed.

Accepted answer

0 additional answers

Your answer

MayankBargali-MSFT 70,936 Reputation points Moderator

2022-10-26T06:12:01.077+00:00

@Ken Fly Thanks for reaching out. Can you please confirm the resource for which you are observing this behavior? Is this azure webapss or azure container apps so the right tags can be added to assist you further.
Gary Anderson 1 Reputation point

2022-10-28T07:35:29.07+00:00

This has been happening to me for about a month now - first on my production app service instance, but now also in my test instance.

I do not believe this is related to any configuration change we have deliberately made as we haven't changed our build or dockerfile for a long time (it's also happening to @Ken Fly so that would be a big coincidence that we both made the same change) and it also probably isn't related to the base docker image as it happened to our live build long before our test build even though they are both built on the same base (mcr.microsoft.com/dotnet/aspnet:6.0).

@MayankBargali-MSFT for me this is happening on my Azure App Service which is Linux Premium V2 and is running a docker container. We witness the same lack of logs, with the "Failed to load container logs: Resource containerlog of type text not found" error message, in both the staging and production slots, when we go to Deployment Center > Logs.

Please feel free to reach out to me for full details of the subscription and instance this is happening to, to aid your investigations. I would have raised it before with Azure Support but we don't have paid support and I couldn't be bothered with the rigmarole of getting a one-time pass from support on Twitter!

In terms of severity, this is really just an inconvenience. Once we deploy a new container I like to jump to the logs tab to check it has fully pulled and started up before switching staging <-> production - as KenFly says we can just jump to Log Stream instead.
MayankBargali-MSFT 70,936 Reputation points Moderator

2022-10-31T07:49:08.093+00:00

@Gary Anderson Thanks for the details. I have added the azure-webapps tag so the team can review it and assist you further.
Ken Fly 46 Reputation points

2022-11-07T00:12:08.433+00:00

sorry for later response. It is azure web application, not container apps
khoai.nguyen 0 Reputation points

2023-06-26T07:16:13.73+00:00

@MayankBargali-MSFT I have the same question in Korea Central with App Service Plan container/I1v2 Docker compose multi container.

I used this article but it is not work. https://learn.microsoft.com/en-us/azure/app-service/tutorial-multi-container-app

Please let me know when it is fixed.

Answer 1

VenkateshDodda-MSFT 24,951 Microsoft Employee Moderator

@Ken Fly Thanks for reaching to Microsoft Q&A. Apologize for the delay in responding on this.

This issue has been identified and our product team has created a fix for this, and the fix will be released soon in the next update (no ETA).

Work around suggested: At this moment the workaround is to access the container logs either from the kudu console or from the log stream feature in the portal.

Alternatively, you can use this REST API to download the container logs file as zip file.

Sample PS script fyi :

$token = "xx"
$headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"
$headers.Add("Accept", "application/zip")
$token = $args[0]
$headers.Add("Authorization", "Bearer ${token}")
$headers.Add("Content-Type", "application/octet-stream")
Invoke-RestMethod 'https://management.azure.com/subscriptions/exx/resourceGroups/xx/providers/Microsoft.Web/sites/xx/containerlogs/zip/download?api-version=2022-03-01' -Method 'POST' -Headers $headers -OutFile "C:\Users\xx\xx\logs.zip"

Feel free to reach back to me if you have any further questions on this.

Gary Anderson 1 Reputation point

2022-11-14T16:12:54.977+00:00

Hi @VenkateshDodda-MSFT . I can confirm that I can now see my container logs, so I assume this fix has been deployed (or it is a transient issue).

Thanks for your help.
VenkateshDodda-MSFT 24,951 Reputation points Microsoft Employee Moderator

2022-11-23T16:40:21.543+00:00

@Gary Anderson Sorry for the delay in my response! Glad to know that your problem has resolved.

I had been discussing on this internally with our product team.

The fix has checked into the next patch and it is expected to be released in early 2023 release. For now, please leverage the workaround provided (above).

Please note that this timeline is just an estimate and is subject to change, depending on a myriad of factors.

Share via

Failed to load container logs: Resource containerlog of type text not found

0 additional answers

Your answer