You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[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
Copy file name to clipboardExpand all lines: articles/container-apps/storage-mounts.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: craigshoemaker
6
6
ms.service: azure-container-apps
7
7
ms.custom: devx-track-azurecli
8
8
ms.topic: conceptual
9
-
ms.date: 04/10/2024
9
+
ms.date: 09/19/2024
10
10
ms.author: cshoe
11
11
zone_pivot_groups: arm-azure-cli-portal
12
12
---
@@ -17,13 +17,13 @@ A container app has access to different types of storage. A single app can take
17
17
18
18
| Storage type | Description | Persistence | Usage example |
19
19
|--|--|--|
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. |
22
22
|[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. |
23
23
24
24
## Ephemeral storage
25
25
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.
27
27
28
28
| vCPUs | Total ephemeral storage |
29
29
|--|--|
@@ -227,15 +227,15 @@ Azure Files storage has the following characteristics:
227
227
* All containers that mount the share can access files written by any other container or method.
228
228
* More than one Azure Files volume can be mounted in a single container.
229
229
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.
231
231
232
232
> [!NOTE]
233
233
> Support for mounting NFS shares in Azure Container Apps is in preview.
234
234
235
235
To enable Azure Files storage in your container, you need to set up your environment and container app as follows:
236
236
237
237
* 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
239
239
](../storage/files/files-nfs-protocol.md).
240
240
* 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.
241
241
* Define a volume of type `AzureFile` (SMB) or `NfsAzureFile` (NFS) in a revision.
0 commit comments