Logs cannot be accessed anymore

Sylvain 216

Recently I cannot access logs anymore in my container instances when the instance is not running.

Previously I could see the logs of the previous runs.

Now it tells me to "navigate to Logs to view container logs", so I set up the thing by giving a log analytics workspace, and of course the request fails with error "InvalidImageRegistryPassword".

I created another instance for testing purposes, now the logs screen can be accessed but nothing is shown and no clue about which table to choose (there is no "ContainerInstancesLogs" table).

Srinud 2,320 Reputation points Microsoft Vendor

2024-09-24T14:31:38.19+00:00
Hi Sylvain,
Thank you for reaching out to us on the Microsoft Q&A forum.
Based upon your query you're encountering a couple of issues with accessing container logs in Azure Container Instances.
Here are some steps you can take to troubleshoot the problems:

The "InvalidImageRegistryPassword" error typically indicates an issue with the credentials used to pull the container image. Please verify that the username and password (or the service principal credentials) for your container registry are accurate.

If you are utilizing Azure Container Registry, consider regenerating the password and updating the Azure Container Instance with the new credentials.

Ensure that your Log Analytics workspace is correctly linked to your container instance and double-check the configuration settings.

For further information, please refer to the following document:
View container group logs in a log analytics workspace via Azure portal - Azure Container Instances | Microsoft Learn.
https://learn.microsoft.com/en-us/azure/container-instances/container-instances-log-analytics?source=recommendations

If you are still facing any issue, please let us know in the comments. We are glad to help you.

If this information is helpful, we would appreciate it if you could click the Upvote on this post.
Srinud 2,320 Reputation points Microsoft Vendor

2024-09-25T09:58:12.23+00:00

Hi Sylvain,

Just checking in to see if you have got a chance to see the comment posted in resolving the issue.

If the information is helpful, please consider by clicking the Upvote on the post.

Thank you.
Sylvain 216 Reputation points

2024-09-25T10:26:59.46+00:00
Hi @Srinud ,

Unfortunately those steps don't help at all :

Credentials of the Container Registry didn't change and were correctly set during the container instance creation (if it wasn't the case the instance would not even start...)

Please tell me how to update a container instance from azure portal (especially how to change credentials) because I don't see how to do it...

The log analytics is not linked and this is exactly the purpose of this topic : the link fails with the error
Srinud 2,320 Reputation points Microsoft Vendor

2024-09-25T12:54:46.9766667+00:00

Hi Sylvain,
Thanks for getting back to us and providing more context.

For the log analytics please refer this document: https://learn.microsoft.com/en-us/azure/container-instances/viewing-logs-in-portal?source=recommendations

For the update container instance, we are looking into it.
Srinud 2,320 Reputation points Microsoft Vendor

2024-09-26T12:02:09.9466667+00:00

Hi Sylvain,

To update the credentials for an Azure Container Instance, you will need to recreate the instance, as Azure does not allow direct updates to existing container instances. When creating the new container instance, please ensure you select the correct credentials and the appropriate Log Analytics workspace to enable logging.

Please find the document for your reference : Quickstart - Deploy Docker Container to Container Instance - Portal - Azure Container Instances | Microsoft Learn.

Thank you.
Sylvain 216 Reputation points

2024-09-26T14:42:07.63+00:00

Well as of today I can't even start my containers anymore, see screenshot :

Edit : seems to be back to normal, containers can be started again.
Srinud 2,320 Reputation points Microsoft Vendor

2024-09-30T18:45:26.68+00:00

Hi Sylvain,

Thank you for the information! The container is functioning normally again. If you encounter any other issues, please let us know; we’re always here to help.

1 answer

Sylvain 216 Reputation points

2024-10-02T14:09:22.5933333+00:00

Hi,

I've been able to update my container, no more credentials error.

But when I consult table ContainerInstanceLog_CL its always empty, logs are not seen.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Logs cannot be accessed anymore

1 answer

Your answer