Replies: 3 comments 27 replies
-
Hi @musteepha, we've been working on some alternative architecture guidance for customers in your same position. Do you have a preference around one of the following options?
Let me know which aligns more to your preferences and I can share some of the preliminary work we've done. Additionally, I'm checking internally as to when the vNET integration will be supported for multi-container (Docker Compose) App Services, and will let you know the response I get. |
Beta Was this translation helpful? Give feedback.
-
Ok, hence the need for path routing, engine now displays after removing the ports configuration |
Beta Was this translation helpful? Give feedback.
-
Hi @DCMattyG hope you are well, seem to be having an issue deploying containers to separate app services: App services can pull image from private ACR over VNET, cosmos is deployed abut keep getting this error on engineApp 23-12-08T01:19:11.739594933Z INFO: Will watch for changes in these directories: ['/ipam'] |
Beta Was this translation helpful? Give feedback.
-
Hi, I have an interesting scenario, we have deployed Azure IPAM into our sandbox and realised we could not use VNet integration on the App service because it is a multi-container App.
What would be the best way to decouple the containers so that they run on multiple App services, and without the nginx loadbalancer
Beta Was this translation helpful? Give feedback.
All reactions