Quickstart: Build an image
Get started with container images by using Azure Pipelines to build an image. All you need to build an image is a Dockerfile in your repository.
You can build both Linux and Windows containers depending on what agent you use in your pipeline. Once you build an image, you can then push it to Azure Container Registry, Docker Hub, and Google Container registry. See push an image to learn more about pushing images to container registries.
- An Azure account with an active subscription. Create an account for free.
- A GitHub account. If you don't have one, sign up for free.
- A GitHub repository with a Dockerfile. If you do not have a repository to use, fork this repository that contains a sample application and a Dockerfile:
Build a Linux or Windows image
Sign in to your Azure DevOps organization and navigate to your project.
Go to Pipelines, and then select New Pipeline.
Select GitHub as the location of your source code and select your repository.
You might be redirected to GitHub to sign in. If so, enter your GitHub credentials. You might be redirected to GitHub to install the Azure Pipelines app. If so, select Approve and install.
Select Starter pipeline. Replace the contents of azure-pipelines.yml with this code. If you are building a Linux app, use
vmImage. You can use
Windows container images can be built using either Microsoft hosted Windows agents or Windows platform based self-hosted agents (all Microsoft hosted Windows platform-based agents are shipped with Moby engine and client needed for Docker builds). Linux container images can be built using Microsoft hosted Ubuntu-16.04 agents or Linux platform based self-hosted agents. Learn more about the Windows and Linux agent options available with Microsoft hosted agents.
Currently the Microsoft hosted MacOS agents can't be used to build container images as the Moby engine needed for building the images is not pre-installed on these agents.
Select Save and run. You'll see a prompt to add a commit message when adding
azure-pipelines.ymlto your repository. Edit the message and then select Save and run again to see the pipeline in action.
Learn more about how to push the image to Azure Container Registry or push it other container registries such as Google Container Registry or Docker Hub. Learn more about the Docker task used in the above sample. Instead of using the recommended Docker task, it is also possible to invoke docker commands directly using a command line task(script)
Clean up resources
If you're not going to continue to use this application, delete your pipeline and code repository.
What pre-cached images are available on hosted agents?
Some commonly used images are pre-cached on the Microsoft-hosted agents to avoiding long time intervals spent in pulling these images from container registry for every job. Images such as
microsoft/aspnetcore-build are pre-cached on Windows agents while
mcr.microsoft.com/azure-pipelines/node8-typescript are pre-cached on Linux agents. The list of pre-cached images is available in the release notes of azure-pipelines-image-generation repository.
How do I set the BuildKit variable for my docker builds?
BuildKit introduces build improvements in the areas of performance, storage management, feature functionality, and security. To enable BuildKit based docker builds, set the DOCKER_BUILDKIT variable.
BuildKit is not currently supported on Windows hosts.
How can I use a self-hosted agent?
How can I create a script-based Docker build instead of using the docker task?
You can use the command
build (or any other Docker command).
docker build -f Dockerfile -t foobar.azurecr.io/hello:world .
This command creates an equivalent image to one built with the Docker task. The Docker task itself internally calls the Docker binary on a script, and also stitches together a few more commands to provide a few more benefits. Learn more in the Docker task documentation.
Is reutilizing layer caching during builds possible on Azure Pipelines?
In the current design of Microsoft-hosted agents, every job is dispatched to a newly provisioned virtual machine (based on the image generated from azure-pipelines-image-generation repository templates). These virtual machines are cleaned up after the job reaches completion, not persisted and thus not reusable for subsequent jobs. The ephemeral nature of virtual machines prevents the reuse of cached Docker layers.
However, you can cache Docker layers with self-hosted agents because the ephemeral lifespan problem is not applicable for these agents.
How to build Linux container images for architectures other than x64?
When you use Microsoft-hosted Linux agents, you create Linux container images for the x64 architecture. To create images for other architectures (for example, x86, ARM, and so on), you can use a machine emulator such as QEMU. These steps show how to create an ARM container image.
- Author your Dockerfile so that an Intel binary of QEMU exists in the base image. For example, the raspbian image already has this.
- Run the following script in your job before building the image:
# register QEMU binary - this can be done by running the following image docker run --rm --privileged multiarch/qemu-user-static:register --reset # build your image
How to run tests and publish test results for containerized applications?
For different options on testing containerized applications and publishing the resulting test results, check out Publish Test Results task.
Advance to the next article to learn how to push an image to a container registry.