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. ACI with static private addresses

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

    10 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 →
  2. 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?

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

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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.

    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 →
  4. Global peering support

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

    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 →
  5. 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
    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. 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…

    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 →
  7. ACI VCPU Pricing is Unclear

    Currently ACI VCPU pricing is unclear, not properly described in FAQ and samples. If a container instance has 3 containers - with VCPU split as follows 1+ 0.1 + 0.1, although the sum is 1.2VCPU, the user will be billed for 48VCPU hours per day for a full day of operation instead of 36VCPU hours.
    In my case this lead to 300 USD higher monthly bill than expected.
    I had a long 2-months support thread (Ref: 120092124000183 ) with Azure Support Team, which proves this is not an evident conclusion.

    The following statement is sufficiently descriptive: "ACI model supports fractional…

    1 vote
    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 →
  8. 1 vote
    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. Monitoring on container restart

    If a container stops working and has a restart policy, it can go on an infinite restart.
    It would be nice to have metric monitoring on that to enable alerting when the container can't self heal.

    2 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 →
  10. Allow container instances that do not expose a port

    ACI currently requires you to expose a port for your container. We have use cases where our containers are background processing jobs that are always on, but we don't need a port for this work.

    Right now AKS seems like the only alternate solution for PaaS hosted containers in Azure, but that's (at the moment) overkill for our use case.

    Our workaround we are trying involves exposing a dead port and overriding health check behavior.

    1 vote
    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 →
  11. 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.

    1 vote
    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. Hopefully, Container groups with GPU becomes GA soon.

    Currently deploying container groups with GPU resources is in preview. It would be great if this feature becomes GA soon.
    https://docs.microsoft.com/en-us/azure/container-instances/container-instances-gpu

    1 vote
    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. Add support for ACI (including vnet integration) to UkWest

    As the title. Just roll out to more regions (including support for vnet deployment since this is an absolute must for security). I personally require UkWest since that's where most of my production infrastructure sits, but I totally understand there is just a desire across the board for more and more regions. Is there a plan to roll out globally for all regions? If not, why not? If yes, when?

    1 vote
    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 →
  14. 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.

    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 →
  15. Expand ACI support beyond 4 CPU core limit, our network router container needs 8 cores

    AKS already supports this requirement, please do the same for ACI.
    We don't need to use K8s for our containerized router, but do need more cores for it so it can meet its network throughput requirements.

    To add this support to ACI by Azure, cannot be a technical challenge as you already do this for AKS and also for the VM based solutions. The issue seems to be that your market analysis tells you most people don't need high powered containers, which is a fair assessment, but there are customers in your networking vendors who could use more cores being…

    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 →
  16. Allow to deploy multi-container from the Portal

    Currently the deployment of multi-container available only via YAML and ARM

    1 vote
    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 →
  17. Support Https out-of-the-box

    This suggestion is to have HTTPS supported at the *.azurecontainer.io level and option to upload a certificate for custom domain so we can CNAME the azurecontainer.io if need be.

    This would be similar to what App Service is doing.

    Currently, having Https on ACI with a valid (i.e. not self-signed) certificate requires a custom domain. Using other services require a non-server-less solution (e.g. APIM consumption can't connect to VNET, same for Function Proxy, AppGw doesn't have a consumption tier, etc.).

    2 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. Support ASG for Containers (ACI)

    Would it be possible to support ASG tags on ACI containers? This could be very useful when setting up a NSG on the subnet that the containers are attached to when using a private VNET.

    2 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 →
  19. Allow automatic scale out of Azure Container Instances

    Allow automatic scale out of Azure Container Instances.

    3 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. 1 vote
    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 →
← Previous 1 3 4 5 6 7 8
  • Don't see your idea?

Azure Container Instances

Categories

Feedback and Knowledge Base