compose-cli icon indicating copy to clipboard operation
compose-cli copied to clipboard

VNet integration

Open evgri243 opened this issue 4 years ago • 3 comments

It would be cool to see a way to specify existing VNet when creating a new ACI instance.

Why? One of the great use-cases for that integration is creating jumpboxes in Azure with VSCode Remote Containers extension.

Recently, there's a motion in Azure on putting all resources behind a vnet to limit any possible malicious access. One of the biggest issues of that approach is in still getting access to that resources on dev environments. Docker ACI context with VNet-join and a proper implementation in VSCode Remote Container extensions will make it easy and flexible.


PS. I can try to help when the integration is open-sourced.

evgri243 avatar Aug 29 '20 23:08 evgri243

Another use case for this is to allow for static IP's to access a docker container group so a DNS A record can safely direct to the container group with SSL. This is an issue that I'm running into.

whimxiqal avatar Nov 29 '20 21:11 whimxiqal

Any new information?

kenoc1 avatar Mar 01 '23 16:03 kenoc1

Im guessing this isnt going to happen as it looks like docker compose are getting rid of the aci / ews integration?

factorialandha avatar Jun 21 '23 13:06 factorialandha