An Azure service that provides customers with a serverless container experience.
Hi Stephen Emm,
Thanks for the update! I'm glad you were able to delete the container group. The issue with mounting the Azure File Share likely caused the container group to be stuck in a "transitioning" state due to the following possible reasons:
Permission Issues: Some container images restrict access to certain system directories, including /mnt, which may have caused the mount failure.
Conflict with System Processes: Some Linux distributions reserve /mnt for temporary mounts, which could interfere with Azure’s mounting process.
Container Runtime Restrictions: Depending on the base image, certain paths may be read-only or restricted, preventing the mount from functioning correctly.
Azure Container Instances (ACI) Specific Behavior: Azure may impose internal constraints on mounting file shares under /mnt, though this is not explicitly documented.
Since mounting the file share to a different location resolved the issue, it's recommended to use paths like /mnt/data, /azurefiles, or /app/data, which may be more suitable for persistent storage in containers.
For more details, refer to the documentation: https://learn.microsoft.com/en-us/azure/container-instances/container-instances-volume-azure-files
If this answer is helpful do click Accept AnswerAnd, if you have any further query do let us know.
Thank You.