You are on page 1of 6

Deploy Azure Container Instances

Lab Details:
1. In this Lab walkthrough, you will create, configure and deploy a Docker
container by using Azure Container Instances (ACI) in the Azure Portal.
2. The container will display a static HTML page.

3. Duration: 00:30:00 Hrs

Tasks:
1. Sign to Azure Portal.

2. Deploy Docker Container using Azure Container Instances..

3. Understand deployment details.

4. Get the Deployed App FQDN(fully qualified domain name).

5. Test the deployment from the browser.

6. Understand the Azure Metric Charts in detail.

Introduction
1. Azure Container Instances are used for Developing apps fast without
managing virtual machines.
2. By running our workloads in Azure Container Instances (ACI), we can focus
on designing and building our applications instead of managing the
infrastructure that runs them.

Lab Steps:
Task 1: Login to Azure Portal
1. If you have logged into any other Azure Account from previous labs or your
own account, please logout of it.

2. Click on the   button.


3. Once the lab creation process is completed, you can see
your username and password.
4. Open a browser tab in incognito mode. Go to the Azure portal by clicking on

the   button or by using URL https://portal.azure.com in


incognito mode.
o Note: It is recommended to use incognito mode to avoid Azure portal
cache related issues.
5. If it automatically logs into any other azure account, please logout of it and
clear cache.
6. Sign in with your given username and password.

7. If login is not working. Click and End Lab and start the lab again.

Task 2: Create Web App using App Services


1. From the All services blade, search for Container instances and Select it.

2. If it shows any error in the page, please wait for 2 minutes and refresh the
page. Backend resources will be created by that time.
3. Click on Add Button

4. In the Basics tab, specify the below settings

o Subscription         : Leave it as default


o Resource Group     : Select the Resource Group with
name resourcegroup_XXXXXXX
o Name             : Enter Unique name mycontainer
o Region            : Select Central US
o Image Source        : Select Quickstart images
 Image        : Select mcr.microsoft.com/azuredocs/aci-
helloworld:latest (Linux)
o Leave other options as default.

o Click on 
5. In the Networking tab, specify the below settings

o Networking Type    : Select Public


o DNS name label    : Enter globally unique name
 Ex : myazurecontainer1244442

Note: our container will be publicly reachable at dns-name-


label.region.azurecontainer.io. If you receive a DNS name label not available error
message following the deployment, specify a different DNS name label (don't use
xxxx) and re-deploy.

 Click on 
6. Verify Summary details in Review + Create tab.

7. Once Verified, Click on  .


8. The Deployment Process will begin Now. Please wait for the deployment to
complete.

9. If deployment fails, it will be usually due to the DNS name label which we


mentioned above in Step 5. As it is globally unique. Change the DNS name
label to globally unique name in Step 5 and redeploy again.
10. Usually it takes 2-5 minutes for deployment to complete.
Task 3: Verify deployment of the container instance
1. we will verify the container instance is running by ensuring that the welcome
page displays.

2. Once the deployment is completed successfully, click on   


button the deployment page.
3. In the Overview page of mycontainer, ensure your
container Status is Running.
4. Locate the Fully Qualified Domain Name (FQDN) and copy it.

o Ex: myazurecontainer1244442.eastus.azurecontainer.io

5. Open FQDN as a new URL tab in the web browser and press Enter. You will
be able to see welcome page as shown below
6. You could also use the container IP address in your browser.

o Ex: http://20.72.140.136/

Task 4: Understand Azure Metric Charts Provided


1. Scroll down in Overview page to see the Azure Metric charts.

2. Hit the FQDN URL 4-5 Times to simulate request response cycle.

3. Please wait for 2-5 minutes and refresh the page if the graph does not show
the traffic details. 
 

4. You can see following charts

o CPU : Provides CPU Usage details.


o Memory : Provides RAM memory usage details.
o Network Bytes Received.
o Network Bytes Transmitted.
5. Above metrics will help us understand the incoming traffic, outgoing traffic and
how its affecting the container.

Completion and Conclusion


1. You have successfully used Azure Portal to deploy an application to a
container in Azure Container Instance.
2. You have successfully tested the deployed Application using FQDN.
 

End Lab
1. You have successfully completed this lab.

2. Click on Logout in Azure Portal by clicking on the logout button in the top
right corner inside Azure Profile.

3. Click on   once you have completed the Lab.

You might also like