Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

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. Support NSG for public ACI instances

    Network Security Groups should be usable with ACI public IPs to enable easy IP whitelisting.

    35 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. ACI with static private addresses

    There is a need for ACI instances to be created with static private addresses. This should survive restarts.

    28 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support setting of hostname

    Currently it seems the hostname of containers are assigned by the kubernetes host to names like wk-caas-53e0cdf0aabd43e791229d05ada1f6f0-99fa4897040e383fe3be53

    It would be helpful if we could set these hostnames at container creation time, rather then using the default name.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Enable private link to work with ACI backend / platform which pulls images from ACR

    Currently private link only work between the container and Azure resources like Key vaults, but it won't work when pulling images from ACR thus ACR will have to enable public network access to the internet without having the capability to whitelist the IP of the ACI backend / platform which responsible pulling the images. This is a big drawback as it is a security concern to most companies.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Enable AppGw to route to containers, even if the container IP address changes automatically

    We have an application gateway configured to route traffic to a container 's private IP address as configured in the AppGW's backend pool. The problem is: the IP address of the container continues to change so we can't rely on this configuration.

    We need a solution where the AppGw always routes to the container, even if the IP address changes.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. windows conteiner vnet

    Windows Container deployed to a vnet would be a very nice feature. The limitation currently is, that windows containers can not be deployed to a vnet and can only get a public ip or no networking.
    Security critical services running on windows containers for internal usage only would be helpful.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Global peering support

    Global peering should be supported so that containers in different regions can communicate

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  9. Increasing limits of Container Instance service in China East 2 region

    There is currently a limit in China East 2 region of at most 2 CPU cores and 8 GB of memory per ACI container.

    Could these limits be increased to 4 CPU core and 14 GB of memory?

    17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Docker-compose compatibility with deploying ACI to a subnet on a virtual network

    Using docker-compose to create an ACI is nice but lacks the ability to deploy to to a virtual network. This is needed for most production cases.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Improved discoverability for private IP addresses.

    Situation:
    Attempting to use Azure Container Instance to host a dot net core application. Application receives UDP messages from multiple IOT devices on a remove network that is connected to azure via a VPN Gateway.

    Issue:
    I could not find a reliable way for the remote network devices to discovery/refer to the container instance as the IP address changes and there is no DNS capability for the instance when using a Private IP.
    There appeared to be no suitable work arounds with load balancers, Application Gateways, or Firewalls.

    Request for improvement:
    Add a way that allows remote resources to reference…

    18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Support for managed identity in a container deployed to a virtual network.

    Are there any plans to remove the limitation of using managed identity with VNET integration?
    We are looking for a way to host a single / small number of containers with VNET integration, so it can communicate with other resources on that VNET via private endnpoints.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Please check the image and registry credential.';'BadRequest':'InaccessibleImage' acr

    Hi
    We deployed a private ACR (SKU Premium).
    We execute from a Linux machine the following command az deployment group create --resource-group myResourceGroup --template-file azuredeploy.json
    We receive in return the following rather wordy error message:
    code": "MultipleErrorsOccurred",
    "message": "Multiple error occurred: 'BadRequest':'InaccessibleImage':'The image 'acrkay01.francecentral.data.azurecr.io/clinform3/backend:latest' in container group 'myContainerGroup' is not accessible. Please check the image and registry credential.';'BadRequest':'InaccessibleImage':'The image 'clinform3/portal:3.7.0-RC4' in container group 'myContainerGroup' is not accessible. Please check the image and registry credential.'."

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Azure policy to deny public facing Azure container service

    Develop a Azure policy with "deny" effect for public facing azure container service to avoid any potential breach

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Mount an Azure Blob in an ACI

    At this moment (March 2021), NFS is available only for “Linux-based Azure Virtual Machine (VM) or a Linux system that runs on-premises”. It would be useful to be able to mount an Azure Blob onto an ACI. Usecase : Allow file transfer to Azure Blob storage through SFTP server (setup on the ACI)

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. environment variables

    Allow environment variables to be maintained independently from image deployment such that they can be updated, added or removed at any time without the need to re-deploy the image.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  18. faultDomain/updateDomain setting for AzureContainerInstances

    I propose to introduce the faultDomain/updateDomain settings for Azure Container Instances like are possible for the VM Availability Sets. Container instances groups with different faultDomain setting would not be run on hosts in the same faultDomain physical hosts. Container instances groups with different updateDomain setting would not be run on the same updateDomain physical hosts. Such setting would prevent a termination of all containers instance groups providing the same high availability service due to host fault or update.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Support the docker --stop-timeout setting in ACI

    I have a container that needs to do some cleanup work when it stops - it needs to run a backup of its config and save it all to an Azure Blob for persistence. In a traditional environment, the developer recommends using the command:

    docker run -d -p 80:80 -p 443:443 --stop-timeout 600 <<containername>>

    ...to launch it, as this allows sufficient time for the container to cleanly close out before a hard shutdown.

    Currently there's no way to support these docker parameters in the ACI configuration. I'd love to be able to set the stop-timeout in the ACI configuration so…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Deploy container group to virtual network without exposing port

    As of February 2021, it's necessary to expose one or more ports on your container group if you want to deploy it to a virtual network. This shouldn't be necessary. I might want the container group to reach intranet resources without exposing the container group to the intranet.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

Azure Container Instances

Categories

Feedback and Knowledge Base