skip to Main Content

I have an F1-tier ASP with a single Web App, and I’m trying to deploy to that web app using a GH Actions workflow. The workflow itself is pretty cookie-cutter; it uses the Deploy a .NET Core app to an Azure Web App template from GitHub with only minor modifications. The workflow has worked well in the past, but is now failing and giving me the following error message in the Deployment Center:

Cleaning up temp folders from previous zip deployments and extracting pushed zip file. There is not enough space on the disk.

I’ve looked at similar questions that seems to suggest that the issue is due to a ZIP deployment being attempted without deleting the previous ZIP file, which does not seem to be true in my case, but even so I’ve looked at the ASP File System Storage and it’s nowhere near its limit. Even if I were to deploy this ZIP without the old one being deleted, it’d still not even be half-way to capacity. I assume the storage limitation is not on the ASP, but somewhere else?

Stranger still is that I can run a deployment directly from Visual Studio and I never seem to encounter this issue. I’m deploying the same application to the same Web App, so how can storage be an issue in one case, but not another? Even a ZIP deployment from VS will go through without issue.

I could perhaps clear space manually in Kudu, but I don’t want to have to do this every time I want to deploy.

I’m scratching my head a little on this, so any help would be appreciated.

2

Answers


  1. Chosen as BEST ANSWER

    We managed to figure this out. I was mistaken on a couple of things when I originally asked the question.

    1. The ZIP files for previous deployments were not being deleted as expected. We saw situations in which ZIPs for 4 previous deployments were all attempting to be stored at once.
    2. The maximum capacity for deployment files is not the same as the maximum capacity of the App Service Plan. The ASP was allocated 1GB, however Kudu local storage (where the ZIPs are stored) was allocated 500MB. In addition to this, even though our ZIP is well below the local storage limit, it is being stored both as a ZIP and as an unzipped directory, which when combined exceeded the 500MB limit. Note the local storage limit is available in Kudu > Environment > System Info.

    Both these issues together meant that it was becoming increasingly common to see failed ZIP deployments due to storage limitations.

    Our solution was two-fold:

    1. Scale Up the Web App from F1 to D1 to increase available storage.
    2. Add the SCM_MAX_ZIP_PACKAGE_COUNT setting to the App Service Configuration (or Environment Variables following the update to Azure) with a value of 1. This setting controls how many ZIP files should be retained in local storage for historic deployments. By default it appears to be 5.

  2. Cleaning up temp folders from previous zip deployments and extracting pushed zip file. There is not enough space on the disk.

    Upgrade the App Service plan and try the same with any plan other than F1 to use more resources appropriately. Refer Article.

    • Navigate to App Service=>App Service Plan=>Select Pricing Plan:

    enter image description here

    • Switch to any other plans to avoid the deployment issues:

    enter image description here

    • The issue could also be due to temporary files stored from the previous deployments. Restart the app to clear the Temp files and deploy your application.

    • Check the deployment logs for the clear error details to know what’s leading to the disk space issue.

    • Delete the existing workflow:

    enter image description here

    • Deploy the app through App Service=> Deployment=> Deployment Center:

    enter image description here

    References:

    Article1

    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search