How to mount a FileShare to a named volume in Azure App Service using Docker Compose?

Question

Hello,
I am using a Docker Compose file (docker-compose.yml) to initiate a container within my Azure App Service environment. My objective is to store the data generated within this container by utilizing volumes and directing them to my Azure Storage Account.

For this I have configured a named Volume in my docker-compose.yml

And used - Path Mappings under Configurations to Mount this Volume to my Azure Storage Account.

With this Path mapping, I am able o see the data in my Azure Storage Account (FileShare). But upon restart of the App Service I see that the files mounted are not getting used by the App Service.

 

I Would like to understand the use of this Volumes in Docker Compose and Mounting (Path Mapping) in Azure App Service.
What happens when an App Service with named Volumes in Docker Compose restarts?

NOTE: When I try to run the docker-compose.yml locally, Things are working good.

 

Answer 1

@Nandha Kumar RP Please note that Docker Compose is not supported for Bring Your Own Storage with Azure App Service.

Limitations

The limitations of custom-mounted storage include:

• Storage firewall is supported only through service endpoints and private endpoints (when VNET integration is used).
• FTP/FTPS access to custom-mounted storage isn't supported (use Azure Storage Explorer).
• Storage account shared access keys are the only means of authentication that are supported; Entra ID and RBAC Roles are not supported.
• Azure CLI, Azure PowerShell, and Azure SDK support is in preview.
• Mapping / or /home to custom-mounted storage isn't supported.
• Don't map the storage mount to /tmp or its subdirectories as this action may cause a timeout during app startup.
• Azure Storage isn't supported with Docker Compose scenarios.
• Storage mounts aren't included in backups. Be sure to follow best practices to back up the Azure Storage accounts.
• NFS support is only available for App Service on Linux. NFS isn't supported for Windows code and Windows containers. The web app and storage account need to be configured on the same VNET for NFS. The storage account used for file share should have "Premium" performance tier and "Filestorage" as the Account Kind. Azure Key Vault is not applicable when using the NFS protocol.
• With VNET integration on your app, the mounted drive uses an RFC1918 IP address and not an IP address from your VNET.

Source:https://learn.microsoft.com/en-us/azure/app-service/configure-connect-to-azure-storage?tabs=basic%2Cportal&pivots=container-linux#limitations

Let us know if you have any further questions or concerns by replying to this message.