Skip to content
BranchesTags

Repository files navigation

ContainerJobExample

A collection of .NET Worker Services packaged as Docker containers and deployed to Azure Container Apps Jobs. Each example demonstrates a different job trigger type and ships structured logs to Application Insights via Serilog.

Example Trigger Description
ManualExample Manual Triggered on-demand via the Azure Portal or CLI
ScheduledExample Schedule (cron) Triggered automatically on a recurring cron schedule

Project Structure

ContainerJobExample/
├── infra/
│   ├── main.bicep                   # Bicep template – Log Analytics, App Insights, Container Apps Env, both Jobs
│   └── main.bicepparam              # Default parameter values (region, app name)
├── src/
│   ├── ManualExample/
│   │   ├── ManualExample.csproj     # .NET 10 Worker Service project
│   │   ├── Dockerfile               # Multi-stage Docker build for ManualExample
│   │   ├── Program.cs               # Host setup with Serilog + Application Insights
│   │   └── Worker.cs                # BackgroundService that runs the manual job logic
│   └── ScheduledExample/
│       ├── ScheduledExample.csproj  # .NET 10 Worker Service project
│       ├── Dockerfile               # Multi-stage Docker build for ScheduledExample
│       ├── Program.cs               # Host setup with Serilog + Application Insights
│       └── Worker.cs                # BackgroundService that runs the scheduled job logic
└── .github/
    └── workflows/
        └── deploy.yml               # CI/CD: build → containerize → deploy (both examples)

Prerequisites

Tool Minimum version
.NET SDK 10.0
Docker any recent version
Azure CLI 2.60+
Bicep CLI 0.27+

An Azure subscription is also required. You can deploy the Azure Container Registry and its dedicated resource group with infra/acr.bicep.

Configuration

Bicep parameters (infra/main.bicepparam)

Parameter Default Description
appName containerjobexample Base name used to derive all Azure resource names
location canadacentral Azure region for all resources
scheduledJobCron 0 0 * * * Cron expression for the scheduled job (default: daily at midnight UTC)

The following parameters are not stored in the param file and must be supplied at deploy time (see CI/CD section below):

Parameter Description
manualContainerImage Full image reference for the manual job, e.g. myacr.azurecr.io/manualexample:run-123
scheduledContainerImage Full image reference for the scheduled job, e.g. myacr.azurecr.io/scheduledexample:run-123
containerRegistryServer ACR login server, e.g. myacr.azurecr.io
managedIdentityResourceId Full resource ID of a pre-existing user-assigned managed identity that has acrPull permissions on the registry

Optional: select a specific user-assigned managed identity

The worker apps support an optional AZURE_CLIENT_ID environment variable:

  • If AZURE_CLIENT_ID is not set, the app uses the default runtime managed identity.
  • If AZURE_CLIENT_ID is set, the app authenticates with that specific user-assigned managed identity.

Set this value on both Container App Jobs if you need to pin the identity explicitly:

az containerapp job update \
  --name <appName>-manual-job \
  --resource-group <your-resource-group> \
  --set-env-vars AZURE_CLIENT_ID=<user-assigned-managed-identity-client-id>

az containerapp job update \
  --name <appName>-scheduled-job \
  --resource-group <your-resource-group> \
  --set-env-vars AZURE_CLIENT_ID=<user-assigned-managed-identity-client-id>

GitHub Actions secrets

Configure the following secrets in Settings → Secrets and variables → Actions on the repository:

Secret Description
AZURE_CREDENTIALS JSON service-principal credentials for azure/login
AZURE_RESOURCE_GROUP Target resource group name
AZURE_LOCATION Azure region (e.g. canadacentral)
APP_NAME Application base name (must match appName in the param file)
ACR_NAME ACR resource name (without .azurecr.io)
ACR_LOGIN_SERVER ACR login server, e.g. myacr.azurecr.io
MANAGED_IDENTITY_RESOURCE_ID Full resource ID of the user-assigned managed identity used for ACR authentication

Local Development

# Restore and run ManualExample locally
dotnet restore src/ManualExample/ManualExample.csproj
dotnet run --project src/ManualExample/ManualExample.csproj

# Restore and run ScheduledExample locally
dotnet restore src/ScheduledExample/ScheduledExample.csproj
dotnet run --project src/ScheduledExample/ScheduledExample.csproj

Build & run the Docker images locally

# ManualExample
docker build --tag manualexample:local --file src/ManualExample/Dockerfile .
docker run --rm manualexample:local

# ScheduledExample
docker build --tag scheduledexample:local --file src/ScheduledExample/Dockerfile .
docker run --rm scheduledexample:local

Infrastructure Deployment (manual)

Create the dedicated ACR resource group and registry first:

az deployment sub create `
  --location canadacentral `
  --template-file infra/acr.bicep `
  --parameters infra/acr.bicepparam

Then deploy prerequisites (managed identity, role assignment, and shared resources):

az deployment sub create `
  --location canadacentral `
  --template-file infra/prereqs.bicep `
  --parameters infra/prereqs.bicepparam `

Finally, deploy the Container Apps jobs into your application resource group:

az deployment group create `
  --resource-group <your-resource-group> `
  --template-file infra/main.bicep `
  --parameters infra/main.bicepparam `
  --parameters `
      manualContainerImage="<acr>.azurecr.io/manualexample:<tag>" `
      scheduledContainerImage="<acr>.azurecr.io/scheduledexample:<tag>" `
      containerRegistryServer="<acr>.azurecr.io" `
      managedIdentityResourceId="<managed-identity-resource-id>" `

CI/CD Pipeline

The workflow at .github/workflows/deploy.yml is triggered manually (workflow_dispatch) and runs three sequential jobs:

  1. Build – restores and publishes both .NET projects, uploads the artifacts.
  2. Containerize – builds Docker images for both examples (tagged with the GitHub run ID) and saves them as artifacts.
  3. Deploy – logs in to Azure and ACR, pushes both images, deploys the Bicep template, then updates both Container App Jobs to use the new images.

Deploying the images

Login to ACR

az acr login --name containerjobtstacr --resource-group containerjobtstacr-rg

Build and push images

docker build -t containerjobtstacr.azurecr.io/manualexample:latest -f src/ManualExample/Dockerfile .
docker build -t containerjobtstacr.azurecr.io/scheduledexample:latest -f src/ScheduledExample/Dockerfile .
docker push containerjobtstacr.azurecr.io/manualexample:latest
docker push containerjobtstacr.azurecr.io/scheduledexample:latest

Deploy jobs

az deployment group create `
  --resource-group containerjobtst-rg `
  --template-file infra/container-job.bicep `
  --parameters infra/container-job.bicepparam `
  --parameters containerImage='containerjobtstacr.azurecr.io/manualexample:latest' `
  --parameters jobName='containermanual-job' `
  --parameters containerName='manualcontainer' `

az deployment group create `
  --resource-group containerjobexampler-rg `
  --template-file infra/container-job.bicep `
  --parameters infra/container-job.bicepparam `
  --parameters containerImage='containerjobexampleacr.azurecr.io/scheduledexample:latest' `
  --parameters triggerType='Schedule' `
  --parameters jobName='containerscheduled-job' `
  --parameters containerName='scheduledcontainer' `

Running the Jobs

ManualExample

After deployment, trigger the manual job from the Azure Portal or via the Azure CLI:

az containerapp job start `
  --name <appName>-manual-job `
  --resource-group <your-resource-group> `

ScheduledExample

The scheduled job runs automatically according to the scheduledJobCron parameter (default: daily at midnight UTC). You can also trigger it manually:

az containerapp job start `
  --name <appName>-scheduled-job `
  --resource-group <your-resource-group> `

About

No description, website, or topics provided.

Resources

Readme
Activity
Custom properties

Stars

1 star

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages