Skip to content

Commit 75898b8

Browse files
authored
Update azure-storage-linux-container-pivot.md
proposing change to troubleshooting to highlight the fix/workaround to mounting NFS share in App Service. Mounting share causes the App Service container to crash
1 parent e2eb028 commit 75898b8

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

articles/app-service/includes/configure-azure-storage/azure-storage-linux-container-pivot.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -225,6 +225,7 @@ To validate that the Azure Storage is mounted successfully for the app:
225225
### Troubleshooting
226226

227227
- The mount directory in the custom container should be empty. Any content stored at this path is deleted when the Azure Storage is mounted, if you specify a directory under */home*, for example. If you migrate files for an existing app, make a backup of the app and its content before you begin.
228+
- When mounting an NFS share, you will need to ensure that Secure Transfer Required is disabled on the storage account. App Service does not support mounting NFS shares when this is enabled. It uses port 2409 and Vnet integration and private endpoints as the security measure.
228229
- If you delete an Azure Storage account, container, or share, remove the corresponding storage mount configuration in the app to avoid possible error scenarios.
229230
- We don't recommend that you use storage mounts for local databases, such as SQLite, or for any other applications and components that rely on file handles and locks.
230231
- Ensure the following ports are open when using virtual network integration: Azure Files: 80 and 445. Azure Blobs: 80 and 443.

0 commit comments

Comments
 (0)