Build Base Image workflow (xinnan-tech/xiaozhi-esp32-server)

The Build Base Image workflow from xinnan-tech/xiaozhi-esp32-server, explained and optimized by Latchkey.

What it does

This is the Build Base Image workflow from the xinnan-tech/xiaozhi-esp32-server repository, a real project running GitHub Actions. It is shown here with attribution under its MIT license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

name: Build Base Image

on:
  push:
    branches:
      - main
    paths:
      - 'main/xiaozhi-server/requirements.txt'
      - 'Dockerfile-server-base'
      - '.github/workflows/build-base-image.yml'

jobs:
  build-base:
    name: Build and push server base image
    runs-on: ubuntu-latest
    permissions:
      packages: write
      contents: read
    steps:
      - name: Checkout code
        uses: actions/checkout@v4

      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v3

      - name: Login to GitHub Container Registry
        uses: docker/login-action@v3
        with:
          registry: ghcr.io
          username: ${{ github.actor }}
          password: ${{ secrets.TOKEN }}

      - name: Build and push server-base
        uses: docker/build-push-action@v6
        with:
          context: .
          file: Dockerfile-server-base
          push: true
          tags: ghcr.io/${{ github.repository }}:server-base
          platforms: linux/amd64,linux/arm64
          cache-from: type=gha,scope=server-base
          cache-to: type=gha,mode=max,scope=server-base
          build-args: |
            BUILDKIT_PROGRESS=plain

      - name: Output image info
        run: |
          echo "✅ Base image built and pushed successfully!"
          echo "📦 Tag: ghcr.io/${{ github.repository }}:server-base"

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: Build Base Image
 
on:
  push:
    branches:
      - main
    paths:
      - 'main/xiaozhi-server/requirements.txt'
      - 'Dockerfile-server-base'
      - '.github/workflows/build-base-image.yml'
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build-base:
    timeout-minutes: 30
    name: Build and push server base image
    runs-on: latchkey-small
    permissions:
      packages: write
      contents: read
    steps:
      - name: Checkout code
        uses: actions/checkout@v4
 
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v3
 
      - name: Login to GitHub Container Registry
        uses: docker/login-action@v3
        with:
          registry: ghcr.io
          username: ${{ github.actor }}
          password: ${{ secrets.TOKEN }}
 
      - name: Build and push server-base
        uses: docker/build-push-action@v6
        with:
          context: .
          file: Dockerfile-server-base
          push: true
          tags: ghcr.io/${{ github.repository }}:server-base
          platforms: linux/amd64,linux/arm64
          cache-from: type=gha,scope=server-base
          cache-to: type=gha,mode=max,scope=server-base
          build-args: |
            BUILDKIT_PROGRESS=plain
 
      - name: Output image info
        run: |
          echo "✅ Base image built and pushed successfully!"
          echo "📦 Tag: ghcr.io/${{ github.repository }}:server-base"
 

What changed

• Run on Latchkey managed runners with one line (runs-on), which apply the fixes below automatically and self-heal transient failures. This example uses latchkey-small; pick the runner size that fits the job.
• Cancel superseded runs when a branch or PR gets a newer push.
• Add a job timeout so a hung step cannot burn hours of runner time.

3 third-party actions are referenced by a movable tag. Pin them to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.

What Latchkey heals here

This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:

• Container pulls and builds

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow