Azure Function shows error 'There is not enough space on the disk'

MWarn 0 Reputation points
2024-04-24T17:18:10.73+00:00

I have an Azure Function written in java which is deployed to Azure via Github Action. In the Azure Portal the following error is shown:

Microsoft.Azure.WebJobs.Script: Error building configuration in an external startup class. System.Private.CoreLib: There is not enough space on the disk. : 'C:\local\Temp\3467f959-0cfe-43d7-88c5-f9df40c89c31\Microsoft.Azure.Functions.ExtensionBundle.Preview.4.18.0.zip'.

This error first occured when I changed the version of 'Microsoft.Azure.Functions.ExtensionBundle.Preview' in host.json to be able to use a Connection to CosmosDB v4. Unfortunately I do not know where to look for the apparently full disk. Can anyone tell me where to look to gather more information?

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,381 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Ryan Hill 26,241 Reputation points Microsoft Employee
    2024-04-25T14:05:22.57+00:00

    Hi @MWarn,

    The size of the disk varies by SKU, e.g. the temporary storage for a Y1 (Consumption) is only 500MB. More than likely, the temporary storage has gotten full. You may be able to use the Kudu console to remove any items. However, it's important to note that the main site and scm site doesn't share the same temporary storage. There is a legacy app setting, WEBSITE_DISABLE_SCM_SEPARATION, that force both sites to use the same storage but it's use isn't recommended.

    I think the best two options is to either use a slot setting or app service plan scaling. You can create a test slot, do the deployment, test, then swap the slots. You can then either decide to keep the slot or delete it. The other option is to scale up your app service plan to EP1, deploy, then scale back down.