Dec 24 / Barry Luijbregts

Getting Started with Azure Container Instances

Working with containers provides a lot of benefits. They are a lot faster to spin up and shut down than Virtual Machines. They run everywhere, which gives you the benefit of having the exact same environment locally as in production. And because they run everywhere, you can run them in any cloud or on-premises, which prevents you from being locked in by any hosting vendor.

My preferred way to run containers is in Azure. And Azure provides a lot of options to run containers in the cloud, each with their own features, pricing and complexity. The simplest way to run a container in Azure is with the service. 
Azure Container Instances allows you to just run a container, without provisioning Virtual Machines and without having to use container orchestrators, like Kubernetes or DC/OS. Container Instances is useful when you just want a container, without orchestration. 

What we are going to do

Lest get started! I’m going to show you how to run an application in a container locally and then publish that to Azure Container Instances. I’ll do this using docker containers. To get started you need the following:

  • Visual Studio
  • Docker for Windows Community Edition
  • Azure subscription

To get a local container into Azure Container Instances, I need to first put it into an intermediary repository that can be accessed by Container Instances. This can be Docker Hubs or something else, like the Azure Container Registry. This is a place that houses container images. This would make our workflow look like this:

Step 1: Adding Docker support to an ASP.NET Core application

I already have an ASP.NET Core application and want to run it in a Docker container. Visual Studio makes this easy for us. Once you have your ASP.NET Core project opened, you can just add Docker support by selecting it from the project menu in Visual Studio. Alternatively, there is a checkbox to enable Docker support for new ASP.NET Core projects. 
Once you do, the resulting solution looks like this:
There’s now a new project, called docker-compose. This contains the docker compose files that will build the image for your web application. Also, there is a Dockerfile file in the web application. This is the actual Docker file that is used to build the Docker image. When you open it, you see that it is based on the microsoft/aspnetcore:2.0 image and adds the application to it. Also, you’ll see that the application is exposed to port 80.

FROM microsoft/aspnetcore:2.0
ARG source
COPY ${source:-obj/Docker/publish} .
ENTRYPOINT ["dotnet", "WebApplication4.dll"]

You need to do one more thing in order to build and run the application locally. You need to change the local Docker server to run Windows based containers. Find the Docker server running on your machine in your applications tray (near the clock), right click on it and click Switch to Windows containers, which I already did (that’s why it says switch to Linux containers in the image below). Unfortunately, this will result in a restart of your system. 
That’s it! Now build and run your solution and you’ll see that the web application will be built and the docker image will be composed and that the application will run locally, in a Docker container. 

Step 2: Push the local image to Azure Container Registry

We now have the application running in a container on our local machine. Now, we need to get this image somewhere so that it can be used by the Azure Container Instances service. We’ll put it in Azure Container Registry, which is a private container repository, hosted in Azure. It is nothing more than storage space for containers. 

First, we’ll create an Azure Container Registry:

1. In the Azure Portal, click the Create a resource button (green plus in the left-upper corner) 
2. Next, search for azure container registry
3. Pick the Azure Container registry from the search results and click Create. The Create container registry wizard appears
a. Fill in a name
b. Create a new resource group or pick an existing one
c. Pick a location
d. Select Enable for the Admin user setting (this enables us to easily authenticate to the registry later on)
e. Leave the SKU to Standard
f. Click Create

And now the registry will be created. Once it is done, we can move on to the next steps.

In order to publish the local Docker image to the registry, we want it to be a release version of the application. So first of all, change the build configuration of the application to Release. A handy way of making sure this works, is to navigate to the Configuration Manager when right-clicking the solution file, and selecting the release configuration.
In my case, the webapplication4 image is the one we want. The one tagged latest was just added after the release build. Now we need to push this image to the Azure Container Registry. In order to do that, we first need to log on to the container registry, like this:


You can find this information in the Access Keys tab of the Container Registry. Here is what this looks like for me (don’t bother to try these credentials, I’ve deleted the repository already):

docker login -u barriescontainerregistry -p DEen2rwlgnYM2sT7W/y57MKNU8iyTqZk+

After logging in, we need to Tag the image before pushing it:

docker tag webapplication4

Now that we have created the tag, we can push the image to the registry:

docker push

That’s it. The image is now in the Azure Container Registry and can now be used by the Azure Container Instance service.

Step 3: Use the image in Azure Container Instances

The image is now in the Azure Container Registry. Let’s create a new Azure Container Instances with the image to see if it will run in the cloud.

1. In the Azure Portal, click the Create a resource button (green plus in the left-upper corner) 
2. Next, search for azure container instance and click Create
3. Now, fill in the first step of the wizard like in the image below. Again, you can find the information for the Container Registry in the Access Keys tab of the Container Registry
4.Now for step 2 of the wizard. Fill it in like in the image below. Be sure to select Windows for the OS type
5.In step 3 of the wizard, everything will be summarized. 
a. Click Create

The Container Instance will now be created. When it is done, you can find an IP address in its overview in the Azure Portal. 
When you now navigate to that address, you’ll see the ASP.NET Core application, because it is exposed to port 80. 

Something to consider: automation

The steps I took to build the container image, push it to Azure Container Registry and get it running in Azure Container Instances are a bit much if you ask me. First of all, I would love to see the tooling evolve to provide us a first-class Visual Studio experience to build images locally and push them to where they need to be – I’m confident that Microsoft will deliver on that.
And secondly, these steps should ideally be automated. You can use something like Visual Studio Team Services to perform the application build steps and compose the image and then push it to Azure Container Registry and to Container Instances. You can read how to do this in the tutorial here. (the article describes pushing to Azure Container Services instead of Container Instances, but the concepts remain the same). 


Azure Container Instances is a simple mechanism to run a container in Azure. You’ve seen that I didn’t have to set up any container orchestrators or clusters nor did I even have to do anything with VMs. 

I think that the abstraction level of the Azure Container Instances service is just right. The tooling to push things to it is not where I would like it to be, but then again, I’m not a big fan of command-line based programming, so this might not be a problem for you.

Also, the service is still in preview and needs some more robustness around the management and monitoring of the containers that it is running. Currently, you don’t really have any insights in how things are doing and if and what you can do about it when things are failing. Surely, this will evolve as Microsoft pushes this service into general availability.
However, this service is definitely worth checking out.
Created with