Hello David Wipper,
Greetings! Welcome to Microsoft Q&A Platform.
It sounds like the issue might be related to the configuration of the volume mount in your container app.
Ensure that the volume is correctly defined in your container app’s configuration. You should have a volume definition in the volumes section of your YAML file.
Make sure that the volume is associated with the container in the volumeMounts section. This is where you specify which container should mount the volume and the mount path.
Double-check that your storage account and file share are correctly set up and accessible. Ensure that the file share is properly linked to your container app environment.
If you are using the Azure CLI, you can update your container app configuration by exporting it to a YAML file, making the necessary changes, and then applying the updated configuration.
Use storage mounts in Azure Container Apps Learn to use temporary and permanent storage mounts in Azure Container Apps
- Tutorial: Create an Azure Files volume mount in Azure Container Apps Learn to create an Azure Files storage mount in Azure Container Apps
- Mount Azure Files volume to container group - Azure Container Instances Learn how to mount an Azure Files volume to persist state with Azure Container Instances
- Mount Azure Storage as a local share - Azure App Service Learn how to attach custom network share in Azure App Service. Share files between apps, manage static content remotely and access locally, etc.
Hope this answer helps! please let us know if you have any further queries. I’m happy to assist you further.
Please "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members