Init container in multi-container azure webservice deployment.

Question

We have a docker-compose file with in it 4 containers:

• Mongo
• Web App
• Web Api
• Initialization

When using a multi-container webapp and using our compose file the app keeps restarting. We found this is due to the app being declared unhealthy because the init container stopped running (as it should).

We've tried configuring its (init container) restart policy to condition: none, but that didn't do the trick. The v2 restart: no syntax didn't help either.

How can I configure a multi-container deployment and have one container run only once and not have that restart the whole web-app constantly?

When we remove the init container, the app remains healthy.

Answer 1

Hi anonymous user,

Multi-container support where a container is being used in a sidecar manner as you are doing is only available on Linux containers, not Windows. If your app service is being hosted in Windows container, please switch it over to Linux. See https://azure.microsoft.com/en-us/blog/app-service-adding-multi-container-capabilities-and-linux-support-for-app-service-environment/ for more information. Even though this blog post references using a Linux ASE, you should be fine with using an app service.

I also noticed you posted the docker-compose on your stackoverflow question as well. If you are hosting your app inside a Linux app service, please let me know as this may be signs of an issue.

Regards,
Ryan