How can we improve Azure Container Instances?

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

90 votes
Sign in
(thinking…)
Sign in with: oidc
Signed in as (Sign out)

We’ll send you updates on this idea

Abhinaba Basu shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

6 comments

Sign in
(thinking…)
Sign in with: oidc
Signed in as (Sign out)
Submitting...
  • Tilo commented  ·   ·  Flag as inappropriate

    is there a list of Docker parameter not support in Azure Container Instance?

  • Aaron Layfield commented  ·   ·  Flag as inappropriate

    This is especially important when using third party images that don't listen on standard ports. It requires having to build your own images. Not ideal at the moment.

  • Radu zidarescu commented  ·   ·  Flag as inappropriate

    ACI should have this feature as docker offers it for local DEV and ACI seems like a cheap, agile DEV env for the cloud when working with containers.

  • Anonymous commented  ·   ·  Flag as inappropriate

    This would be FANTASTIC converting to Kubernetes was going to take a a bit of dev effort we’d rather not dedicate at the moment

  • Anonymous commented  ·   ·  Flag as inappropriate

    Currently you need to specify every single exposed port in configuration or CLI. We'd like to be able to specify port ranges, e.g. 8080-8089 for a cleaner configuration and scripts.

Feedback and Knowledge Base