Azure Container Instances

Have feedback for Azure Container Instances? Submit your idea or vote up an idea submitted by others. All of the feedback you share here will be monitored and reviewed by the Azure Container Instances team. Remember that this site is only for feature suggestions and ideas. If you have technical questions or issues, please submit them to our GitHub issues page or on StackOverflow .

How can we improve Azure Container Instances?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Cache the downloaded container image in the Container Instances (preview)

    Each time I start a new container, the image is pulled from the repository. Even if I start 10 times the same image. I would like to have the image cached (maybe on the resource group level) so that I only get the penalty of pull once.

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

    We’ll send you updates on this idea

    under review  ·  17 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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

    planned  ·  6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support auto-delete of ACI when container exits normally

    When an ACI container exits normally and the restart-policy is Never you should automatically delete the ACI. Currently it sticks around with a status of Terminated.

    In my scenario I want to spin up ACI's to drain an Azure queue. When the queue is empty my ACI workers will exit and I do not want to have to go and clean up the ACI remnants afterwards. They should cleanly remove themselves as if they never existed.

    This can be an option if there are scenarios where this is undesirable.

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

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Want to support running Windows Server 1709 (and later) image

    Currently, Azure Container Instances cannot running Windows Server 1709 container image, because running Windows Server 2016 on Azure Container Instances. (I guess that.)

    Microsoft said 1709 not supported on Win2016 of Host OS ver as follows:
    * https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility

    My feedback: I want to choose Semi-Annual Channe version's host in Azure Container Instances.

    Semi-Annual Channe is so nice solution for cloud platform because faster update, include more feature, lightweight images. However some customers want to solid OS like as LTSC. So that. I want to choose both version's host.

    Why 1709? 1709's image is more lightweight than LTSC and other Windows…

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

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow an ACI container to update itself when the image is updated

    This scenario is currently not supported and an update requires the container to be deleted (which forces an IP. Address change)

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

    We’ll send you updates on this idea

    8 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Virtual Network for Windows Containers

    ACI is one of the few options to deploy Windows Containers in GA. The need to do Windows Containers is coming from enterprise customers which also happen to be the ones that require VNET support in my experience.

    VNET integration is in preview but only supports linux containers.

    Thanks MS team!

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

    We’ll send you updates on this idea

    planned  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Larger memory sizes - at least 32GB - best 64GB

    Current memory sizes are too small for my usage.

    I need something to start quickly, load a 1-50GB dataset - process it in memory for half an hour and deallocate.

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

    We’ll send you updates on this idea

    9 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Support Managed Disks

    The title describes feature.
    Currently ACI is not suitable for hosting databases, but if you give us ability to mount Managed Disks it would allow us to hust hunderds of databases.
    I saw this post https://medium.com/@seanmckenna_47871/aci-pm-here-d59cde58890a and it says "We intend to eventually support other volume types, such as Azure Managed Disks.". Do you still have plans to support Managed Disks?

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  9. Use the same exposed public ip for outbound traffic start from the containergroup

    I have some question related to the Public IP used by container group create from Azure Container Instance. Actually the container group can expose public ip (set ipAddress.type = “Public”) which is used to access from external, but for the traffic start from the container group I found it does use the assigned exposed public ip. I’d like to check if possible to using the same exposed public ip for the outbound traffic starting from the container group ? if not, how the outbound traffic public ip is assigned to the container group ? Thanks previously for your kindly response.

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

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. EventGrid notification when ACI container stops

    I'd like to be notified when my container (group) terminates. An event grid notification would be ideal. It should include the exit code as part of the payload

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

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. ACI support for privileged container

    Make possible to lauch contaner in privilege mode to allow loading of kernel modules and other feautures.

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

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow ACI instances to use a static IP address when using a private VNet

    When configuring ACI instances that will exist in a private VNet, allow us to specify the IP address to use so we can configure DNS names externally to resolve to these servers.

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

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Access docker.sock inside container instance

    This is more a matter than an idea. My question is if it is possible to access docker.sock on a container instance inside a container group.
    In my specific case I need the docker.sock so that Traefik (https://traefik.io/) can discover the remaining instances.
    Any suggestions and ideias would be nice :)

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. Expand port number

    Only allowing for 5 ports to be open on a container is very limiting. Please let us open at least 8 if not no limit.

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

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Give us outgoing IPs or Allow Route Tables

    We need to know the outbound IPs for containers running in ACIs.

    Other cloud providers allow you to do this through a managed NAT.

    We've even tried using out own vNet in an attempt force tunnel the request through our on-premise network. However, we cannot do this as you cannot use Route Tables and Service Endpoint delegation together.

    This is really disappointing especially since AWS and Google Cloud both allow static IPS and managed NATs.

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

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Support ACI in South America Region

    When should we expect to see South American support for ACI?

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

    We’ll send you updates on this idea

    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Enable Containers in VNETs to Have a Public IP

    Enable Containers in VNETs to Have a Public IP

    It would be useful for containers to have a public IP and also be present in a VNET, for the use case of any type of proxy device - be it web proxy or VPN, IPS.

    At present you can be entirely in VNET with no Public IP or just a container with a PIP and no access to VNET

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

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Allow passing arguments to commands executed in a container via 'az container exec ... --exec-command "<command>"'

    According to the documentation at https://docs.microsoft.com/en-us/azure/container-instances/container-instances-exec as of October 2018, there is a restriction on executing commands in a running container: "... you cannot pass command arguments."

    Please allow the passing of arguments.

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

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Allow creating multiple mounts from the same volume

    Currently ACI requires to have distinct volumes for each mounts which is not convenient since in case of Azure Files it requires creating a number of Azure Storage Shares.

    It would be great to mount the different volume paths like that:

    ```
    {
    "volumeMounts: [{
    "name": "myVolume",
    "mountPath": "/var/lib/waagent/"
    "volumePath": "/waagent/"
    },{
    "name": "myVolume",
    "mountPath": "/etc/path/"
    "volumePath": "/path/"
    }]
    }
    ```

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

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow Environment Variables with a dot from powershell

    Trying to create a container instance from powershell using New-AzureRmContainerGroup commandlet, but I cannot pass environment variables that have a dot in their name. Consider the following hastable that is passed to the commandlet:
    $environmentVars = @{"api.key"="APIKEYGOESHERE";"api.addrs.addr.name"="1.2.3.4"}

    Running the command and passing the above hashtable as a parameter gives me the following error:

    New-AzureRmContainerGroup : The environment variable name in container 'TEST-owaspzap' of container group 'TEST-owaspzap' is invalid. A valid environment variable name must start with
    alphabetic character or '_', followed by a string of alphanumeric characters or '_' (e.g. 'my_name', or 'MY_NAME', or 'MyName').

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

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4
  • Don't see your idea?

Azure Container Instances

Feedback and Knowledge Base