Skip to content

Commit 326793d

Browse files
[Git issue 122739 : Error with Storage Set (NFS): Discussed with Antony, verified the procedure as per his suggestion and reviewed for the freshness pass. ms.date updated
1 parent afb530a commit 326793d

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/container-apps/storage-mounts.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: craigshoemaker
66
ms.service: azure-container-apps
77
ms.custom: devx-track-azurecli
88
ms.topic: conceptual
9-
ms.date: 04/10/2024
9+
ms.date: 09/19/2024
1010
ms.author: cshoe
1111
zone_pivot_groups: arm-azure-cli-portal
1212
---
@@ -17,13 +17,13 @@ A container app has access to different types of storage. A single app can take
1717

1818
| Storage type | Description | Persistence | Usage example |
1919
|--|--|--|
20-
| [Container-scoped storage](#container-scoped-storage) | Ephemeral storage available to a running container | Data is available until container shuts down | Writing a local app cache. |
21-
| [Replica-scoped storage](#replica-scoped-storage) | Ephemeral storage for sharing files between containers in the same replica | Data is available until replica shuts down | The main app container writing log files that are processed by a sidecar container. |
20+
| [Container-scoped storage](#container-scoped-storage) | Ephemeral storage available to a running container | Data is available until container shuts down | Writing a local app cache. |
21+
| [Replica-scoped storage](#replica-scoped-storage) | Ephemeral storage for sharing files between containers in the same replica | Data is available until replica shuts down | The main app container writing log files that a sidecar container processes. |
2222
| [Azure Files](#azure-files) | Permanent storage | Data is persisted to Azure Files | Writing files to a file share to make data accessible by other systems. |
2323

2424
## Ephemeral storage
2525

26-
A container app can read and write temporary data to ephemeral storage. Ephemeral storage can be scoped to a container or a replica. The total amount of container-scoped and replica-scoped storage available to each replica depends on the total amount of vCPUs allocated to the replica.
26+
A container app can read and write temporary data to ephemeral storage. Ephemeral storage can be scoped to a container or a replica. The total amount of container-scoped and replica-scoped storage available to each replica depends on the total number of vCPUs allocated to the replica.
2727

2828
| vCPUs | Total ephemeral storage |
2929
|--|--|
@@ -227,15 +227,15 @@ Azure Files storage has the following characteristics:
227227
* All containers that mount the share can access files written by any other container or method.
228228
* More than one Azure Files volume can be mounted in a single container.
229229

230-
Azure Files supports both SMB and NFS protocols. You can mount an Azure Files share using either protocol. The file share you define in the environment must be configured with the same protocol used by the file share in the storage account.
230+
Azure Files supports both SMB (Server Message Block) and NFS (Network File System) protocols. You can mount an Azure Files share using either protocol. The file share you define in the environment must be configured with the same protocol used by the file share in the storage account.
231231

232232
> [!NOTE]
233233
> Support for mounting NFS shares in Azure Container Apps is in preview.
234234
235235
To enable Azure Files storage in your container, you need to set up your environment and container app as follows:
236236

237237
* Create a storage definition in the Container Apps environment.
238-
* If you are using NFS, your environment must be configured with a custom VNet and the storage account must be configured to allow access from the VNet. For more information, see [NFS file shares in Azure Files
238+
* If you're using NFS, your environment must be configured with a custom VNet and the storage account must be configured to allow access from the VNet. For more information, see [NFS file shares in Azure Files
239239
](../storage/files/files-nfs-protocol.md).
240240
* If your environment is configured with a custom VNet, you must allow ports 445 and 2049 in the network security group (NSG) associated with the subnet.
241241
* Define a volume of type `AzureFile` (SMB) or `NfsAzureFile` (NFS) in a revision.

0 commit comments

Comments
 (0)