4 min read

Running your containerized application on the Microsoft Azure cloud platform

In this post, I will demonstrate one option to run your containerized .NET application on one of the most popular cloud providers on earth (Microsoft Azure).
Running your containerized application on the Microsoft Azure cloud platform
Running your containerized application on the Microsoft Azure cloud platform
Host your portfolio site with GCP Cloud Storage in a few steps
In this post, I will walk you through 5 steps to host your portfolio profile on GCP using Cloud Storage & Load Balancer, check it out
In this post, I will demonstrate one option to run containerized .NET Core application on one of the most popular cloud provider on earth (Microsoft Azure). We will create a simple .NET application, containerize it and then run it on the cloud.


  • Microsoft Azure account with an active subscription.
  • GitHub account.
  • Visual Studio to create .NET application.
  • Docker Desktop up & run locally.
  • Basic knowledge of Docker & Azure.

1. Create our ASP.NET web application and run it locally.

First, create a new ASP.NET Core web application using Visual Studio as below steps:

Create a new project & select the ASP.NET Core Web App template
Name your project and select Framework then click Create

Use .NET Core 3.1 LTS  framework and leave Enable Docker unchecked (we will write Dockerfile manually to learn). After the project is successfully created, run it locally (Ctrl + F5) and verify it.

ASP.NET web app successfully run locally as image

2. Containerize ASP.NET web app with Docker

In this step, we will create a Dockerfile so that our application can run as a container (actually, we can just check Enable Docker in the project creation steps, but I want to write it manually so we can have a better understanding).

Create a Dockerfile in the project directory like below:

FROM mcr.microsoft.com/dotnet/aspnet:3.1 AS base

FROM mcr.microsoft.com/dotnet/sdk:3.1 AS build
COPY ["MyDemoWebApp/MyDemoWebApp.csproj", "MyDemoWebApp/"]
RUN dotnet restore "MyDemoWebApp/MyDemoWebApp.csproj"
COPY . .
WORKDIR "/src/MyDemoWebApp"
RUN dotnet build "MyDemoWebApp.csproj" -c Release -o /app/build

FROM build AS publish
RUN dotnet publish "MyDemoWebApp.csproj" -c Release -o /app/publish

FROM base AS final
COPY --from=publish /app/publish .
ENTRYPOINT ["dotnet", "MyDemoWebApp.dll"]

Base image: mcr.microsoft.com/dotnet/aspnet:3.1, listening on port 80.

Navigate to solution folder and run docker build command to build docker image from Dockerfile (noted that I run the command from the parent folder, not where the Dockerfile located, that why I need to have -f flag).

$ docker build -f MyDemoWebApp/Dockerfile -t mydemowebapp .

Next, run the container using docker container run command and map port 8080 on the host to port 80 of the container.

$ docker run -dt --name my-demo-web-app -p 8080:80 mydemowebapp

$ docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED         STATUS         PORTS                  NAMES
dab93a9b1fcb   mydemowebapp   "dotnet MyDemoWebApp"   9 minutes ago   Up 9 minutes>80/tcp   my-demo-web-app

Verify the container by accessing http://localhost:8080/, it should show the Welcome page as above image.

3. Tag docker image and push to docker hub repository

To make the demo simple, we will use Docker Hub as our repository, in real-world projects, the private repository option will be used instead (Azure Container Registries, Amazon ECR...).

Open Docker hub and create a public repository for our demo app:

Create image repository on Docker Hub
$ docker tag mydemowebapp:latest trungtlt/my-demo-web-app:latest

$ docker push trungtlt/my-demo-web-app:latest
The push refers to repository [docker.io/trungtlt/my-demo-web-app]
d0179e95459b: Preparing
5f70bf18a086: Preparing
8343c61fec2c: Preparing
4d26b9c21cee: Preparing
11280ad13be6: Preparing
2ad0addaac90: Preparing
068c0c45d9f4: Preparing
f18b02b14138: Preparing
2ad0addaac90: Waiting
068c0c45d9f4: Waiting
f18b02b14138: Waiting
5f70bf18a086: Layer already exists
4d26b9c21cee: Layer already exists
d0179e95459b: Layer already exists
8343c61fec2c: Layer already exists
f18b02b14138: Layer already exists
2ad0addaac90: Layer already exists
068c0c45d9f4: Layer already exists
11280ad13be6: Pushed
latest: digest: sha256:7e1b258b88c84190fbca55203ac46129b22e7903d2981ac48bd53208f2588cbc size: 1999
Docker image successfully push to docker hub repository

4. Provision compute resource on Microsoft Azure (Azure Container Instance)

Azure Container Instance is a compute service on Azure that allows us to run containers without managing servers (container as a service - CAAS), more about ACI can be found here: https://docs.microsoft.com/en-us/azure/container-instances/container-instances-overview.

Open Azure portal at https://portal.azure.com/ and navigate to Container instances service (search "Container instances").

Create new container instance as above image

Subscription: select your own subscription, resource group: create new, container name: my-demo-web-app, Region: Southeast Asia, Image source: Docker Hub or other registries, Image type: Public, Image: {image URL}, OS type: Linux.

Go to the Networking tab and configure as below image:

Configure Networking tab as above image
Azure container instance created successfully at http://my-demo-web-app.southeastasia.azurecontainer.io/

We just reached the final step to run our containerized application on Azure, we can verify it by accessing container instance FQDN, it will be {name}.southeastasia.azurecontainer.io.

Congrats, we successfully create the asp.net application, dockerize it, publish it to the Docker Hub repository and then run it on Azure cloud. Hope you enjoy this journey and see you in the next posts.