Support for port mapping
In docker we can map ports as
docker run -d -p 80:8080 foo/bar
This is super helpful for cases where the container has fixed code to listen to some port like say 8080 but you want to expose that at a different port on the container.
I do not see that option in the CLI. There should be something like
az container create --ports 80:8080
This is a backlogged feature. We do support symmetrical port mapping today.
Tony Ding commented
This is a must have feature for ACI
Just adding my voice to this thread. This is a showstopper for using this service unfortunately.
Same here, we have a port instead the container but want to make that to a port outside. Another container we have is a SQL Server container. the sql server container runs on 1433 so mapping that to port 80 in the normal container instance create doesnt make since
Microsoft needs to really start addressing the normal application development flow. Most people who are using containers need port mapping. That you are saying it doesn't support it and that it is unplanned just shows how out of contact you are with what everyday people are doing. If you don't support it, then offer a solution. If your solution is that we change our containers to inherently work on port 80, if that's your solution, it isn't one.
Seth Lyons commented
Port mapping is a basic feature of scaling with containers, instead of building separate container images to make use of the same container group.
David Dorsett commented
Seriously??? This is basic container functionality. Halfway done.... so much of Azure seems this way (this-or-that only works on this kind of sub-thing). You guys need to spend less time on new stuff and more time on your technical debt.
Rodrigo Gomez commented
This is a must have feature. A basic MVP feature.
Johannes Norrbacka commented
Outrageous! A true basic key feature that makes the whole thing close to unusable. As a customer of Azure, with all of its "supposed" feature sets, one cannot stop getting the feeling of being told: You can do anything you want, but you have to do it this specific way with these limitations. It's like saying: "Sure, you can use math on our platform, but we do not support multiplication, division, subtraction or addition. Are not Azure awesome?"
Anthony BOUQUET commented
+1 for this feature, it should be a must have, me and my colleague don't understand why it hasn't been implemented as it's a standard and one of the most used feature of docker with volume mapping.
I wish this was there, this is pretty standard requirement, I am surprised why it isn't there yet...
Asymmetric port mapping (eg 80:8080) is a must have feature for this context. It's been > 2 years, please consider including in the next sprint.
Illegal as **** amd mine
I would love to see this feature
Pretty basic thing that supported by locker docker runner
Same issue here - this feature is quite essential IMO.
Bernd R commented
Same issue here - I would love to use this feature instead of an nginx reverse proxy in a side car.
Marcelo Wippel commented
Same issue here. Having the port mapping option in the portal would be great.
Evandro Pomatti commented
Container Instances is a great service but port mapping is a convenient feature that should be implemented.
Same problem here, how can i specify this?
Robert Emsbach commented
Based on the comment saying it was supported now I tried it cloud shell (bash and powershell) and in my local powershell CLI. Everywhere I get the error:
az container create: error: argument --ports: invalid int value: '80:8080'
Where / on which version is it supposed to be supported? @MacKenzieOlson