Docker compose App not running with permanent storage in Azure App Services

Georg 0 Reputation points
2023-08-31T07:16:28.0866667+00:00

I created a Docker Compose App in Azure App Service. When I start the App without specifying permanent storage, it is working as expectet (GLPI interface for installation shows up). After I mount a Azure File Share as permanent storage with the name fsglpi and add the line like this to my compose file

volumes:

  • fsglpi:/var/www/html/glpi

the app doesn't start anymore (error 404, later error 503). While browsing the fileshare I could see part of the files necessary where written into it, but only a fraction of them. Maybe somebody else had this issue, or can point me to a recent tutorial how to correctly configure this. Or maybe there is a better way to host compose Apps in Azure?

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
6,840 questions
{count} votes

1 answer

Sort by: Most helpful
  1. SnehaAgrawal-MSFT 18,206 Reputation points
    2023-09-04T14:20:50.6233333+00:00

    @Georg

    Yes, this is specific to wordpress an example of docker compose, they have mentioned it here as below -

    For this tutorial, you use the compose file from Docker, but you'll modify it to include Azure Database for MySQL, persistent storage, and Redis. The configuration file can be found at Azure Samples.

    In the sample below, note that depends_on is an unsupported option and is ignored.

    For supported configuration options, see Docker Compose options.

     

    To mount storage account, you may try container instances - https://learn.microsoft.com/en-us/azure/container-instances/container-instances-volume-azure-files

    1 person found this answer helpful.
    0 comments No comments