Azure AppServices wont start after deployment: error during container init: unable to join session keyring: unable to create session key: disk quota exceeded

Michael Schmitz 0 Reputation points
2024-02-29T12:16:18.59+00:00

Hello,

we are currently using a P5mv3 service plan to host various linux ASP.NET Core apps (.NET 8.0).
We are experiencing some issues, when deploying updates to our apps.

The apps wont come back online after deployment with the following error message:

Docker API responded with status code=InternalServerError, response={"message":"failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: unable to join session keyring: unable to create session key: disk quota exceeded: unknown"}

The only solution working thus far, is to manually scale down the plan and then back up (or expliticly restarting the underlying VM via Diagnostics). This of course restarts all web apps on the service plan and is not prefered in any way.

We are running ~60 apps/slots in total on the plan, but do not exceed 20% avg CPU utilization/30% peak. The docs state, that the number of apps is only limited by CPU usage. But then it should be not an error.
I managed to track the issue to be related to the setting of /proc/sys/kernel/keys/maxkeys, but this setting can not be modified for an appService.

Any pointers would be greatly appreciated.

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
7,785 questions
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.