VS Code deployment error: "Offset to Central Directory cannot be held in an Int64"

Question

VS Code deployment error: "Offset to Central Directory cannot be held in an Int64"

Zalán Joób 5

I'm deploying a Flask Web App to a Linux B1 App Service with one instance. My zip package size is under 900MB.
When the web app is running I get the following error: "Offset to Central Directory cannot be held in an Int64", but if I stop the App Service and retry, it deploys without any problems.

My local project directory is 4GBs including the environment(3.5GB of this data are GeoTIFF files). The Web App currently doesn't generate any excess data while it's running.

My quotas tab shows that I have plenty of available space in the App Service with the app successfully deployed and running.

User's image

One of the deployment logs:

hh:24:11 Project: Zip package size: 843 MB

hh:24:13 Project: Fetching changes.

hh:24:14 Project: Cleaning up temp folders from previous zip deployments and extracting pushed zip file /tmp/zipdeploy/499c6545-c5e9-48f1-9cf2-982df9c59b5f.zip (267.84 MB) to /tmp/zipdeploy/extracted

hh:24:14 Project: Offset to Central Directory cannot be held in an Int64.

hh:24:18 Project: Deployment failed.

I've noticed that the pushed zip files size changes between 250 and 400 MB during these failed deployments.

Thank you for the help in advance!

Ajay Kumar N 28,261 Reputation points Microsoft Employee Moderator

2023-01-27T13:58:52.9533333+00:00

@Zalán Joób ,

Apologies for the delayed response. Based on the information you have shared, I understand in B1 App Service Plan (ASP), you’re running the WebApp 1 instance.

To better assist you on this, just to clarify:

1.    Do you have more WebApps in the same ASP?

2.    Does this issue occur only with this specific WebApp or other WebApps?

3.    Does this issue occur only when deploying via VS code?

4.    How was the package zipped? (.zip file, or Gzip or something else?)

5.    Any difference in how the package is zipped from previous deployments?
Ajay Kumar N 28,261 Reputation points Microsoft Employee Moderator

2023-01-30T19:25:50.4566667+00:00

@Zalán Joób ,

Just checking in to see if you had got a chance to see the previous responses. Kindly share more details to help you better.

--

To benefit the community find the right answers, please do mark the post which was helpful by clicking on Accept Answer.
Zalán Joób 5 Reputation points

2023-01-30T20:03:02.67+00:00
@ajkuma

Sorry for the late answer and thank you for your help!

I only have this one Web App in the ASP and I don't have deployment slots either.

This is my only Web App currently. But I'll try testing it elsewhere too!

I have tried deploying with a .zip package while the App was running. I've got a "No space left on device" error during the Oryx Build. I've had this error later with VS Code deploy attempts too.

During my .zip deploy attempt I packaged the directory with the PowerShell Compress-Archive command. I used the default settings in VS Code.

When deploying with VS Code I right-clicked on the web app in the extension menu and chose the "Deploy to Web App" option

I have the latest version of Azure Tools. I'll try to scale up and share my experience as soon as possible! But I don't currently need more than one instance of B1 for my application.

Azure diagnostics didn't find any deployment problems.

I have tried changing around as many things as possible, but I always get the same result: The deployment succeeds if the Web App has been stopped before the deployment and fails if it runs while deploying.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Ajay Kumar N 28,261 Reputation points Microsoft Employee Moderator

2023-01-31T20:08:58.1933333+00:00

@Zalán Joób , Thanks for the follow-up and additional info.
As a quick check, you may scale-up ( or scale-out), deploy and test the behavior, later switch/downgrade to B1. Let us know know how it goes, ( we may need additional info about your WebApp), I'll follow-up with you further.

--(I see that you were able to delete' your duplicate comment fine). I' have relayed the feedback to our Q&A platform team about the visibility of the comment deletion option.
Alexandre Olech 0 Reputation points

2024-02-17T16:19:22.3266667+00:00

Hello, I'm new to Azure and I am getting the same error when I try do deploy my web application directly from visual studio code. As you can see, my most heavy file is 400 mo. I'm using a B1. Is there something wrong in my configuration ?

Wouter 5

Deploying to a standard webapp using github, seeing the same errors recently:

Run azure/webapps-deploy@v3
  with:
    slot-name: staging
    app-name: app-demo-service-staging
    package: deploy_package
  env:
    ARTIFACT_NAME: DemoService.zip
    SOLUTION_DIR: backend/DemoService
    APP_NAME_VAR_NAME: BACKEND_DemoService_APP_NAME
    WORKER_APP_NAME_VAR_NAME: BACKEND_DemoService_WORKER_APP_NAME
    RESOURCE_GROUP_VAR_NAME: BACKEND_DemoService_RESOURCE_GROUP
    DATA_ACCESS_DIR: DataAccess
    CSPROJ_DIR: Service
    CSPROJ_FILE: Service.csproj
    KEYVAULT_NAME_VAR_NAME: KEYVAULT_NAME
    DB_CONTEXT_VAR_NAME: BACKEND_DemoService_DB_CONTEXT
    DB_CONNECTIONSTRING_KEYVAULT_KEY_VAR_NAME: BACKEND_DemoService_DB_CONNECTIONSTRING_KEYVAULT_KEY
    DB_CONNECTIONSTRING: Server=tcp:demo-db-server.database.windows.net,1433;Initial Catalog=db-demo-service;Persist Security Info=False;User ID=db_user;***;MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;;Command Timeout=3600
    ZIP_FOLDER: deploy_package
    NUGET_PACKAGES: /home/runner/work/DemoProject/DemoProject/.nuget/packages
    DOTNET_ROOT: /usr/share/dotnet
Predeployment Step Started
Deployment Step Started
Starting deployment for web app...
Package deployment using OneDeploy initiated.
{
  id: 'temp-1234567890',
  status: 3,
  status_text: '',
  author_email: 'N/A',
  author: 'N/A',
  deployer: 'OneDeploy',
  message: 'OneDeploy',
  progress: '',
  received_time: '2025-09-16T11:49:30.9447715Z',
  start_time: '2025-09-16T11:49:30.9447715Z',
  end_time: '2025-09-16T11:49:36.6795075Z',
  last_success_end_time: null,
  complete: true,
  active: false,
  is_temp: true,
  is_readonly: false,
  url: 'https://app-demo-service-staging.scm.azurewebsites.net/api/deployments/latest',
  log_url: 'https://app-demo-service-staging.scm.azurewebsites.net/api/deployments/latest/log',
  site_name: 'app-demo-service-staging',
  provisioningState: 'Failed'
}
Fetching changes.
Cleaning up temp folders from previous zip deployments and extracting pushed zip file C:\local\Temp\zipdeploy\0d03chze.zip (55.49 MB) to C:\local\Temp\zipdeploy\extracted
Offset to Central Directory cannot be held in an Int64.
Error: Failed to deploy web package to App Service.
Error: Deployment Failed, Package deployment using ZIP Deploy failed. Refer logs for more details.
App Service Application URL: https://app-demo-service-staging.azurewebsites.net

3 answers

Your answer

Ajay Kumar N 28,261 Reputation points Microsoft Employee Moderator

2023-01-27T13:58:52.9533333+00:00

@Zalán Joób ,

Apologies for the delayed response. Based on the information you have shared, I understand in B1 App Service Plan (ASP), you’re running the WebApp 1 instance.

To better assist you on this, just to clarify:

1. Do you have more WebApps in the same ASP?

2. Does this issue occur only with this specific WebApp or other WebApps?

3. Does this issue occur only when deploying via VS code?

4. How was the package zipped? (.zip file, or Gzip or something else?)

5. Any difference in how the package is zipped from previous deployments?
Ajay Kumar N 28,261 Reputation points Microsoft Employee Moderator

2023-01-30T19:25:50.4566667+00:00

@Zalán Joób ,

Just checking in to see if you had got a chance to see the previous responses. Kindly share more details to help you better.

--

To benefit the community find the right answers, please do mark the post which was helpful by clicking on Accept Answer.
Zalán Joób 5 Reputation points

2023-01-30T20:03:02.67+00:00

@ajkuma

Sorry for the late answer and thank you for your help!

I only have this one Web App in the ASP and I don't have deployment slots either.

This is my only Web App currently. But I'll try testing it elsewhere too!

I have tried deploying with a .zip package while the App was running. I've got a "No space left on device" error during the Oryx Build. I've had this error later with VS Code deploy attempts too.

During my .zip deploy attempt I packaged the directory with the PowerShell Compress-Archive command. I used the default settings in VS Code.

When deploying with VS Code I right-clicked on the web app in the extension menu and chose the "Deploy to Web App" option

I have the latest version of Azure Tools. I'll try to scale up and share my experience as soon as possible! But I don't currently need more than one instance of B1 for my application.

Azure diagnostics didn't find any deployment problems.

I have tried changing around as many things as possible, but I always get the same result: The deployment succeeds if the Web App has been stopped before the deployment and fails if it runs while deploying.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Ajay Kumar N 28,261 Reputation points Microsoft Employee Moderator

2023-01-31T20:08:58.1933333+00:00

@Zalán Joób , Thanks for the follow-up and additional info.
As a quick check, you may scale-up ( or scale-out), deploy and test the behavior, later switch/downgrade to B1. Let us know know how it goes, ( we may need additional info about your WebApp), I'll follow-up with you further.

--(I see that you were able to delete' your duplicate comment fine). I' have relayed the feedback to our Q&A platform team about the visibility of the comment deletion option.
Alexandre Olech 0 Reputation points

2024-02-17T16:19:22.3266667+00:00

Hello, I'm new to Azure and I am getting the same error when I try do deploy my web application directly from visual studio code. As you can see, my most heavy file is 400 mo. I'm using a B1. Is there something wrong in my configuration ?

Answer 1

Next Six 5

i do face the same issue on my VSC with azure tools. it works perfectly fine until today. we have built reactjs project deployed to the 2 different instances as below:

i have

Offset to Central Directory cannot be held in an Int64.

on my S1, while i have another error on my P1v2 as shown below

Number of entries expected in End Of Central Directory does not correspond to number of entries in Central Directory.

Sergey 5 Reputation points

2023-12-14T07:55:45.7166667+00:00

I'm experiencing the same errors during the deployment. Started to appear on Dec 13th in the evening.

Answer 2

Zalán Joób 5

It deploys successfully with a 2-instance B2 plan.

I managed to solve the problem for a 1-instance B1 plan by deploying my big static files one by one with Azure CLI and changing the URLs in the program to reference the previously deployed static files in my wwwroot folder. It cut down the deployment .zip package size to just 11MB(from 850MB). I was able to deploy the smaller .zip even while the Web App was running. My advice for anyone with the same problem is to deploy the static files via FTP. It's slower, but you don't have to input each command one by one.

Thank you for the help! The problem for my specific use case is solved, but I can supply more information if my feedback is of any use!

Ajay Kumar N 28,261 Reputation points Microsoft Employee Moderator

2023-02-02T20:46:24.65+00:00

@Zalán Joób , Thanks for the follow-up and sharing the solution that worked for you with the community.

Please share your observations and suggestions, it will surely benefit the community. I'll also relay the feedback internally to our product team. Much appreciate your feedback!

I have converted your comment to answer now.

To benefit the community find the right answers, please do mark the post which was helpful by clicking on Accept Answer. [you cannot accept your own answer, please check this Q&A doc: Accept answer]

Answer 3

Adding more info:

Just to highlight, if multiple apps are in the same ASP, they all share the same VM instances. If you have multiple deployment slots for an app, all deployment slots also run on the same VM instances. In a nutshell, the ASP is the scale unit of the App Service Apps. If the plan is configured to run 4 VM instances, then all apps in the plan run on all 4 instances.

Ensure that you have the llatest version of Azure Tools installed.
If you have a small instance, Scale-up and check if it makes any difference.
Note that, TAR and GZIP formats are not supported and the ZIP file can be at most 1GB
( I understand the file size for you is under 1 GB). You may leverage App Service diagnostics from Azure Portal> Navigate to your App Service app in the Azure Portal. (screenshot below)
- In the left navigation, click on Diagnose and solve problems - Review - “Configuration and Management and “Availability and Performance” options.

Share via

VS Code deployment error: "Offset to Central Directory cannot be held in an Int64"

3 answers

Your answer