Need more info on behaviour and usage of stateful containers

[mcintyre321]

It's a bit unclear how a container which requires persistent state (e.g. a sql container) will behave - will the data be stored in a permanent fashion anywhere? How would one go about backing up the data from an instance like this?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: d0615dff-cbdd-0583-739e-72eadbb629bf
• Version Independent ID: c927ed72-dad6-4265-758a-cb6f5d0f4256
• Content: Deploy custom image, multi-container, or built-in image - Azure App Service
• Content Source: articles/app-service/containers/choose-deployment-type.md
• Service: app-service
• GitHub Login: @msangapu
• Microsoft Alias: msangapu

[shashishailaj]

@mcintyre321 Thank you for your feedback . We will investigate and update this thread.

[DashleenBhandari-MSFT-zz]

@mcintyre321 , We recommend to use Azure SQL/Azure DB for MySQL to customers.
There are a lot of articles explaining the problems you might face (for example https://vsupalov.com/database-in-docker ) and why you should not run PROD DBs in a container (specially if you use a Container Orchestrator that might move your containers around)

[mcintyre321]

In your samples there are application with mysql and redis containers. Are these samples there to demonstrate what can be done, rather than what should be done?

…

On Mon, 25 Mar 2019, 12:23 DashleenBhandari-MSFT, ***@***.***> wrote: @mcintyre321 <https://github.com/mcintyre321> , We recommend to use Azure SQL/Azure DB for MySQL to customers. There are a lot of articles explaining the problems you might face (for example https://vsupalov.com/database-in-docker ) and why you should not run PROD DBs in a container (specially if you use a Container Orchestrator that might move your containers around) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#27591 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAQ0-kJRx0fBFH8ggUaIVYclC3bcTuWLks5vaL_MgaJpZM4b-3VE> .

[mcintyre321]

Hi, this is a screenshot from the Azure portal, from adding a linux/container based app service. As you can see, the sample container app includes an mssql container.

it seems strange to have this as a sample if it's an unsupported, not recommended scenario

[mcintyre321]

Now I'm confused. Your colleague @DashleenBhandari-MSFT says "you should not run PROD DBs in a container", but you suggest the mysql container is prod ready?

How is the mysql container data persisted? It looks like tutorial says how to back the wp container is backed by disk, but not the mysql instance (or am i missing something?)

[mcintyre321]

Thanks - it would be good to have some explicit text describing the lifecycle of the containers, so that we can make judgements about which containers it is sensible to run, and which should be replaced by PAAS, or backed by disk.

Also some information about how the containers will interact (or not) in multi-instance app services. E.g. Redis is less useful than in a distributed setup if you have a single, non-persistent instance per web server.

[msangapu-msft]

#please-close