Setting WEBSITE_RUN_FROM_PACKAGE to 1 and having cache

Question

Setting WEBSITE_RUN_FROM_PACKAGE to 1 and having cache

KoyaRishi-2480 0

Hi, I recently enabled zip deployment for my NextJS application and set WEBSITE_RUN_FROM_PACKAGE to 1. Having read the documentation I know it makes the wwwroot folder read only.

However, I have some static files in Next which used to be cached under wwwroot/cache. I am now getting errors in my logs:

Failed to update prerender cache for 1642cd5060d84196a6e3e165c43d49cde1caef2ddbaab05d155de5f70d8c5bdf Error: ENOENT: no such file or directory, mkdir '/home/site/wwwroot/app-name/standalone/apps/app-name/.next/cache'

Is there any way to move the cache folder outside of wwwroot?

Shree Hima Bindu Maganti 4,775 Reputation points Microsoft External Staff Moderator

2025-03-19T16:30:36.3+00:00

Hi @unknown,
When deploying a Next.js application to Azure App Service with WEBSITE_RUN_FROM_PACKAGE=1, the wwwroot directory becomes read-only, leading to errors when Next.js attempts to write cache files to this location. To resolve this, you can configure Next.js to use a writable directory for caching, such as /home/site/temp. This involves updating the next.config.js file to set the cache directory to /home/site/temp/next-cache. Additionally, setting the NEXT_PRIVATE_CACHE_DIR environment variable in Azure to the same path ensures that Next.js recognizes the new cache location. It's also advisable to include logic in your application to create the cache directory at runtime if it doesn't exist, preventing potential errors. These adjustments align with Azure's guidelines on writable directories and Next.js's caching mechanisms, ensuring your application functions correctly without encountering permission issues.
for ref:Run your app from a ZIP package - Azure App Service

Building Your Application: Caching - Next.js

Understanding the Azure App Service file system - GitHub

next.config.js: cacheHandler | Next.js
Let mi know if you any further any assistances.
KoyaRishi-2480 0 Reputation points

2025-03-20T15:07:31.8333333+00:00

@Shree Hima Bindu Maganti Thank you for the response. I cannot see where in next.config.js you would set this. In terms of the keys that are available as options, nothing here stands out just for the cache. The build output directory (distDir) includes the cache folder. In my case distDir: dist
Shree Hima Bindu Maganti 4,775 Reputation points Microsoft External Staff Moderator

2025-03-20T15:44:11.5033333+00:00

Hi @unknown,
Next.js does not expose a direct configuration key in next.config.js to change the cache directory. By default, the .next/cache folder is included within distDir, which is read-only in Azure when WEBSITE_RUN_FROM_PACKAGE=1 is enabled. To resolve this, instead of modifying next.config.js, you should set the NEXT_PRIVATE_CACHE_DIR environment variable in Azure to a writable location such as /home/site/temp/next-cache. This ensures Next.js stores its cache outside the wwwroot directory. You can configure this by navigating to Azure Portal → Your Web App → Configuration → Application Settings, adding NEXT_PRIVATE_CACHE_DIR with the value /home/site/temp/next-cache, and restarting your app. Additionally, ensure your application creates this directory at runtime if it doesn’t exist by adding a check in your server entry script using fs.mkdirSync(). This approach aligns with Next.js caching mechanisms and Azure's file system limitations, ensuring your application runs smoothly.
Next.js Configuration Guide Azure App Service File System

Deploying ZIP Packages in Azure
Let mi know if you any further any assistances.
KoyaRishi-2480 0 Reputation points

2025-03-21T13:43:45.27+00:00

Hi @Shree Hima Bindu Maganti

I have set WEBSITE_RUN_FROM_PACKAGE=1 and NEXT_PRIVATE_CACHE_DIR=/home/site/temp/next-cache

For the purposes of testing I created the folder /temp/next-cache inside the site folder using Kudu. I restarted the application and ran it, however I am still see failed logs.

Failed to update prerender cache for 786b4299dac2b2765d6646091d3a3108fc367081fcee54ecefe29afa82ba528c Error: ENOENT: no such file or directory, mkdir '/home/site/wwwroot/app-name/standalone/apps/app-name/.next/cache'
Harshitha Veeramalla 1,301 Reputation points Microsoft External Staff Moderator

2025-03-26T10:29:33.1466667+00:00

unknown Please check your private messages and provide us with requested information to check and assist you further on this.

Your answer

Shree Hima Bindu Maganti 4,775 Reputation points Microsoft External Staff Moderator

2025-03-19T16:30:36.3+00:00

Hi @unknown,
When deploying a Next.js application to Azure App Service with WEBSITE_RUN_FROM_PACKAGE=1, the wwwroot directory becomes read-only, leading to errors when Next.js attempts to write cache files to this location. To resolve this, you can configure Next.js to use a writable directory for caching, such as /home/site/temp. This involves updating the next.config.js file to set the cache directory to /home/site/temp/next-cache. Additionally, setting the NEXT_PRIVATE_CACHE_DIR environment variable in Azure to the same path ensures that Next.js recognizes the new cache location. It's also advisable to include logic in your application to create the cache directory at runtime if it doesn't exist, preventing potential errors. These adjustments align with Azure's guidelines on writable directories and Next.js's caching mechanisms, ensuring your application functions correctly without encountering permission issues.
for ref:Run your app from a ZIP package - Azure App Service

Building Your Application: Caching - Next.js

Understanding the Azure App Service file system - GitHub

next.config.js: cacheHandler | Next.js
Let mi know if you any further any assistances.
KoyaRishi-2480 0 Reputation points

2025-03-20T15:07:31.8333333+00:00

@Shree Hima Bindu Maganti Thank you for the response. I cannot see where in next.config.js you would set this. In terms of the keys that are available as options, nothing here stands out just for the cache. The build output directory (distDir) includes the cache folder. In my case distDir: dist
Shree Hima Bindu Maganti 4,775 Reputation points Microsoft External Staff Moderator

2025-03-20T15:44:11.5033333+00:00

Hi @unknown,
Next.js does not expose a direct configuration key in next.config.js to change the cache directory. By default, the .next/cache folder is included within distDir, which is read-only in Azure when WEBSITE_RUN_FROM_PACKAGE=1 is enabled. To resolve this, instead of modifying next.config.js, you should set the NEXT_PRIVATE_CACHE_DIR environment variable in Azure to a writable location such as /home/site/temp/next-cache. This ensures Next.js stores its cache outside the wwwroot directory. You can configure this by navigating to Azure Portal → Your Web App → Configuration → Application Settings, adding NEXT_PRIVATE_CACHE_DIR with the value /home/site/temp/next-cache, and restarting your app. Additionally, ensure your application creates this directory at runtime if it doesn’t exist by adding a check in your server entry script using fs.mkdirSync(). This approach aligns with Next.js caching mechanisms and Azure's file system limitations, ensuring your application runs smoothly.
Next.js Configuration Guide Azure App Service File System

Deploying ZIP Packages in Azure
Let mi know if you any further any assistances.
KoyaRishi-2480 0 Reputation points

2025-03-21T13:43:45.27+00:00

Hi @Shree Hima Bindu Maganti

I have set WEBSITE_RUN_FROM_PACKAGE=1 and NEXT_PRIVATE_CACHE_DIR=/home/site/temp/next-cache

For the purposes of testing I created the folder /temp/next-cache inside the site folder using Kudu. I restarted the application and ran it, however I am still see failed logs.

Failed to update prerender cache for 786b4299dac2b2765d6646091d3a3108fc367081fcee54ecefe29afa82ba528c Error: ENOENT: no such file or directory, mkdir '/home/site/wwwroot/app-name/standalone/apps/app-name/.next/cache'
Harshitha Veeramalla 1,301 Reputation points Microsoft External Staff Moderator

2025-03-26T10:29:33.1466667+00:00

unknown Please check your private messages and provide us with requested information to check and assist you further on this.

Share via

Setting WEBSITE_RUN_FROM_PACKAGE to 1 and having cache

Your answer