Azure Container Instances (ACI) allows developers to easily run containers on Azure without managing servers. Developers can choose the VM types that they want to run their containers in. We are excited to announce that ACI now supports GPU enabled containers, enabling developers to run intensive jobs required for machine learning.
Powered by the open source Virtual Kubelet technology, Azure Kubernetes Service (AKS) virtual node allows you to elastically provision additional pods inside Container Instances that start in seconds. With a few clicks in the Azure portal, turn on the virtual node feature and get the flexibility and portability of a container-focused experience in your AKS environment without needing to manage the additional compute resources. And since your Azure Container Instances containers can join the same virtual network as the rest of your cluster, you can build Kubernetes services that seamlessly span pods running on virtual machines (VMs) and Azure Container Instances.
Azure Container Instances supports Linux containers in three new regions: Australia East (New South Wales), East US 2 (Virginia), and Central US (Iowa). These additions bring the total to nine regions across the globe.
Azure Container Instances supports multiple new features in the release of the June API 01-06-2018 including multiple container groups per single YAML, secrets can now be passed in environment variables, liveness probes and more.
We are proud to announce the general availability of Azure Container Instances (ACI) – a serverless way to run both Linux and Windows containers. ACI offers you an on-demand compute service delivering rapid deployment of containers with no VM management and automatic, elastic scale. When we released the preview last summer of ACI, it was the first-of-its-kind and fundamentally changed the landscape of container technology. It was the first service to deliver innovative serverless containers in the public cloud. As part of today’s announcement, I am also excited to announce new lower pricing, making it even less expensive to deploy a single container in the cloud. ACI also continues to be the fastest cloud-native option for customers in the cloud, getting you compute in mere seconds that also provide rich features like interactive terminals within running containers and an integrated Azure portal experience.
Azure Container Instances now includes support for running containerized tasks. Here are the updates for February 2018:
DNS name labels for containers: Configure a reliable endpoint for each container by placing a DNS name label through the REST API or Azure CLI 2.0.
az container create --resource-group MyResourceGroup --name myalpine --image alpine:latest --ports 80 443 --dns-name-label contoso
Streaming container logs with Azure CLI 2.0: Read your container state and log output by attaching to your container from Azure CLI 2.0.
az container attach --resource-group MyResourceGroup --name myalpine
Container restart policies: Designate containers to always restart, restart only on failure, or never restart.
Various volume types for mounting: Mount Azure Files, gitRepo, emptyDir, and secret volumes.
Guidance on container failures: Error messages provided for container instance failures have been refined and extended to improve self-debugging.
Support for the Southeast Asia region: Deploy container instances from Southeast Asia in addition to East US, West US, and West Europe.