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 .

  1. 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/"

    }]
    }
    ```

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

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. MSI support for Container Instances inside VNETs

    When deploying a simple container instance with --assign-identity set, I'm able to retrieve Tokens (via curl or anything else).
    However, deplying the exact same instance into a VNET will break this functionality. The Container Instance still has a identity assigned, yet it is not able to reach 169.254.169.254 anymore.

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

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Update New-AzContainerGroup to allow multiple containers in ACI

    In AZ CLI you can specify a yaml file containing multiple images when deploying an Azure Container Instance.

    This functionality should be made available using Azure Powershell, as it would be useful for writing lightweight deployment scripts in Azure Functions or even Automation. Currently New-AzContainerGroup can only be used to create single-container ACI resources.

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

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Support docker-compose to deploy multiple container deployment on ACI

    Adding support of docker-compose to ACI would be a huge benefit as it is the standard approach for multi-container setups.

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

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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. 'myname', or 'MYNAME', or 'MyName').

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

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Multiple windows containers in a container group

    Add support for deploying multiple windows containers within a container group. Currently only a single windows container supported, or multiple Linux containers.

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. Enable controlling the user for which Azure Files shares are mounted

    Shares from Azure Files are mounted in directories accessible only to the "root" user. If the container is configured to run its application as a non-root user, the entrypoint has to become a shell script that can assign appropriate permissions to the share directory. Running a script to chmod/chown every file on the share is very slow.

    It would be much easier to use shares from Azure Files if there was a way to control what user the share was mounted for.

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

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Mount secret from Key Vault

    It would be great if I could specify a secret in a Key Vault as the value for a secret mount in ACI. That way I do not have to encode the value in the ARM file or on the command line.

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

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. MSI support for Windows Containers

    It seems that most of the part is supported on Linux containers.
    But it would be a nice feature to have MSI support for Windows containers to begin with.

    I get this error when trying to add identity to Windows container following this guide: https://docs.microsoft.com/en-us/azure/container-instances/container-instances-managed-identity

    "Managed service identity is not supported for Windows container groups."

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. Support Stopping and Starting Container Groups from Az PowerShell Module

    It doesn't appear that the Az PowerShell module has any support to start, stop or restart a container group.

    This can be done with the Azure CLI with the az container stop, az container start, and container restart commands.

    Please provide equivalent functionality in the Az PowerShell module, (and close the other gaps like az container exec)

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow scaling number of containers in container group

    Currently It's possible to add new containers in container group via incremental deployments, but it's not possible to remove containers from group afterwards.

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

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Support for volumes on ACI Windows

    ** Request
    Support for external volumes on ACI Windows

    ** Business Needs
    Many user would like to keep the image small but refer many data.
    Availability for external volume mount may be good solution for the business needs.

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Support metrics for Windows Containers

    Please support basic metrics like average CPU en Memory usage for windows containers. I'ts very hard at the moment to see if we are hitting any limits of the container.

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Support port range

    Only support opening 5 ports is very limited. We are using a mountebank service that supports starting a service at any port asked by a user.

    As we can expose a range of ports on docker, please consider supporting this feature.

    docker run -p4500-4600:4500-4600

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Application insights for ACI

    Better monitoring - overview of the Instances that ran (successfully or failed)

    better means to analyse from one source -like application insights the details / logs of the container

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add support for faster cores, comparable to D- and H-Series VM's

    We are currently able to run our jobs in 20 seconds with a D3v2 Cloud Service VM, while it takes 33 seconds for ACI with 4 cores.

    ACI should be improved to compete with VM's used by Cloud Services and other resource types.

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. Support Availability Zones for Azure Container Instance

    The idea is that if we want to use Azure Container Instance (ACI) in our solution which support HA redundancy, currently it's not possible because there's no availability zone support. Spawning two container instances in same region could result in single point of failure if the region is down. Spawning in two different regions may work but it's definitely a concern on the pricing.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Deploy Container Group with Log Analytics from Powershell

    I can do this from the CLI or YAML, but not Powershell. CLI and Powershell need all the same features. https://docs.microsoft.com/en-us/azure/container-instances/container-instances-log-analytics

    4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Nano server (SAC) on ACI

    Currently ACI only support LTSC-based image. (Azure Container Instances supports Windows images based only on Long-Term Servicing Channel (LTSC) versions. To mitigate this issue when deploying Windows containers, always deploy LTSC-based images.)

    Would be good to support SAC images as all Nano server base images are in SAC. (https://hub.docker.com/r/microsoft/nanoserver/)

    4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Improve filesystem speed

    While it's a pure container service and everything should be mastered up front, many off-the-shelf containers (jenkins) do an initial setup that can be quite time consuming on slower infrastructure.

    It would be nice if ACS had faster disk access just to ensure reliable behaviour.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Azure Container Instances

Categories

Feedback and Knowledge Base