You want builds to run in Azure and push images to your registry without Docker on the CI agent. What should you use?
Why B is the answer
Azure Container Registry Tasks
ACR Tasks builds images inside the registry service itself, so the CI agent needs no Docker daemon.
In detail
- Container Registry Tasks build images in Azure.
- The CI agent does not need Docker.
- Tasks can also run on a base image update.
Use case
An illustrative scenario, not a real incident.
A CI agent has no Docker. A Container Registry Task builds the image in Azure and pushes it to the registry.
See it in different ways
flowchart LR A["Source code"] --> B["ACR Tasks build"] B --> C["Azure Container Registry"] C --> D["App Service, Container Apps or AKS"]
mindmap
root((Container hosting))
Container Apps
Serverless
Scale to zero
Revisions
AKS
Full Kubernetes
Node pools
App Service
Simple web API
Deployment slots
Container Registry
Stores images
Build taskssequenceDiagram participant P0 as CI agent participant P1 as ACR Tasks participant P2 as Registry P0->>P1: Build this context P1->>P2: Push image P2-->>P0: Image ready
Key point: Registry Tasks build images in Azure.
Why the other options are wrong
- A. Azure Container Apps jobs
- Jobs run containers, and they are not an image build service.
- C. Azure App Service deployment slots
- Slots swap web app versions.
- D. Azure Kubernetes Service node pools
- Node pools run workloads.