In a word, no. But as is usually the case, there's far more to be said--and for you to consider, to get you to the right solution for you.
First, if you do more study of containerized deployment, you'll find this challenge (wanting to put two services into one container, and why it's frowned upon) is not at all unique to cf but instead a common challenge for folks moving to containers.
Folks have often wanted to run a web server and an app server (like cf or tomcat, or even node and more) in a single image/ container. Or maybe they want to run the app server and the db in one. Or all 3.
The thing is, containers are NOT lightweight vms, suited to running many things at once: they are designed such that each container serves a single purpose, a single primary process (PID 1, in linux terms).
As such, much about container deployment presumes that approach, so that trying to to shoehorn two or more server processes into one image/container is an anti-pattern. You can certainly TRY to force it with the cf and add-ons containers, but nothing from Adobe will show how to do it.
And usually when faced with such a challenge, it's time to perhaps question your own presumptions and choices. 🙂 And even sticking with Azure, you have more choices than just ACI.
But let me note first that there ARE resources showing deployment of Docker Compose into ACI, such as:
Or if one was ardently uninterested in using compose files, Azure also supports multi-container deployments on ACI via a simple yaml file:
https://learn.microsoft.com/en-us/azure/container-instances/container-instances-multi-container-yaml
BUT ACI has its own warts and may not really be the best (or most economical) way to deploy containerized web apps on Azure.
Have you looked also at Azure web apps for containers (under Azure app service), which also supports multi-container deployment (whether via compose or not):
https://learn.microsoft.com/en-us/azure/app-service/quickstarts multi-container
And you mention wanting to use Azure pipelines. Here's a tutorial on using that to run multi-container deployments on that Azure app service:
https://learn.microsoft.com/en-us/training/modules/deploy-kubernetes/
Another is:
https://techcommunity.microsoft.com/t5/windows-dev-appconsult/automate-the-deployment-of-a-multi-con...
Or consider instead the newer Azure container apps, which is out of preview only this year:
https://learn.microsoft.com/en-gb/azure/container-apps/overview
Or see also:
Depending on your ultimate use case for containerized cf (dev? testing? prod? short-lived? 24x7), either of these options could be far cheaper to run than ACI.
To be clear, under the covers those both offer an implementation of a very opinionated kubernetes deployment - - without you having to know much about k8s. That's a pro to some, a con to others. But each different implementation (from ACI to those to the others) offers different/generally increasing capabilities.
Then of course there's the option to run full-blown kubernetes in Azure, for those who may need it, as in AKS.
FWIW, the author of that last post has one that offers an overview of several ways to run containers in Azure, in 2022:
Let us know how you end up going, if at all.
/Charlie (troubleshooter, carehart.org)
13
Replies
AdChoices