Using Docker, Azure DevOps and Azure Container Instances we are going to setup a simple pipe-line that will build our image from code to Docker image, tag and push that image to a private Azure Container Registry and deploy the latest version of said container to a Azure Container Instance. I use this personally for a few small projects like my personal dashboard. I edit, run and test the code on my local machine using Docker and then commit the code my DevOps GiT repository.
This looks a little like this:
Some pre requirements. This guide assumes you are using Azure DevOps and DevOps GiT. You also need to link your DevOps environment to your Azure Subscription. Details for DevOps and DevOps GiT are here:DevOps Setup
And more on adding Azure to your DevOps environment is here:
So before we get started, check if you have the following: Add Azure to DevOps Pipeline
- Active Azure environment;
- Azure DevOps;
- Azure DevOps Service set up to connect to your Azure environment;
- Az CLI installed on you system (see: Installing Azure CLI) . You can also use the Azure Web CLI from your Azure Portal.
Some notes, I’m using
<Placeholder> to indicate places where you need to provide code. I’m also using Azure CLI in BASH so I’ll be using
\ to do linebreaks. Replace them with backticks
` if you’re using PowerShell.
Setting up Azure
In your Azure environment we are going to setup a Private Azure Container Registry and a Resource Group to deploy your Container instance, get started by login in:
After login in create your resource group
az group create \ --location "West Europe" \ --name RG-ContainerInstance \ --tags CiCDTutorial
Now we are going to create the Private Container Repository
az acr create \ --name PrivateRepository \ --resource-group RG-ContainerInstance \ --sku Basic \ --admin-enabled true \ --tags CiCDTutorial
Now (from the Azure Portal) go to
Dashboard > Container registries > PrivateRepository - Access keys :
Note down the following:
- Login server
You’ll need this in your Build pipeline.
Now we’re done on the Azure side. Time to switch over to Azure DevOps
Setting up DevOps Pipeline
In Azure DevOps navigate to your project and go to
Pipelines > Builds. We are going to setup a pipeline that is triggered by a commit to the Master Branch. Select
New and then
New Build Pipeline .
Select your source (in this case I’m using Azure Repos)
After selecting your repo chose a
After this you are presented with the basic pipeline YAML. Replace the YAML with the following code
# Starter pipeline # Start with a minimal pipeline that you can customize to build and deploy your code. # Add steps that build, run tests, deploy, and more: # https://aka.ms/yaml trigger: - master pool: vmImage: 'ubuntu-latest' steps: - script: echo Building and Pusing image displayName: 'Building and Pusing image' - task: Docker@2 inputs: containerRegistry: 'Azure Docker Repository' repository: 'YourRepository' command: 'buildAndPush' Dockerfile: '**/Dockerfile' tags: 'latest' - task: AzureCLI@2 inputs: azureSubscription: '<YourSubscriptionName> (<YourSubscriptionID>)' scriptType: 'bash' scriptLocation: 'inlineScript' inlineScript: | az container delete \ --name YourContainerInstance \ --resource-group RG-ContainerInstance \ --yes - task: AzureCLI@2 inputs: azureSubscription: '<YourSubscriptionName> (<YourSubscriptionID>)' scriptType: 'bash' scriptLocation: 'inlineScript' inlineScript: | az container create \ --image <Login server>/YourRepository \ --registry-login-server <Login server> \ --registry-username <Username> \ --registry-password <Password> \ --resource-group RG-ContainerInstance \ --name YourContainerInstance \ --cpu 0.5 \ --memory 1 \ --ports 3030 \ --environment-variables GEMS=uptimerobot \ --restart-policy always \ --dns-name-label YourDNSLabel \ --restart-policy always \ --tags CiCDTutorial
In this case I’m deploying a Docker image and giving it
0.5 CPU ,
1 GB RAM, Parsing in some ENV variables and exposing
port 3030. You can customize this to your liking. You can find more details on creating Azure Container Instances on the Docs page
This pipline will do the following steps:
- Build a Docker image acoarding to the Dockerfile in the root of your GiT Repo;
- Tag that image as
latestand push it to you private Repository
- In case that your current Container Instance is running the first Azure CLI command will delete it;
- Deploy a new Container Instance named
YourContainerInstancewith a few extra variables.
After the deployment you can check if your image is running using
az container list --output table
Found this useful? Consider sponsoring me or buying me a cup of coffee at KoFi