Skip to content
Latchkey

🐳 Docker (Multi-Arch) workflow (TangSengDaoDao/TangSengDaoDaoServer)

The 🐳 Docker (Multi-Arch) workflow from TangSengDaoDao/TangSengDaoDaoServer, explained and optimized by Latchkey.

C

CI health: C - fair

Point runs-on at Latchkey and get run de-duplication, job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.

Grade your own workflow free or run it on Latchkey →
Source: TangSengDaoDao/TangSengDaoDaoServer.github/workflows/ghcr.ymlLicense Apache-2.0View source

What it does

This is the 🐳 Docker (Multi-Arch) workflow from the TangSengDaoDao/TangSengDaoDaoServer repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.

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

The workflow

workflow (.yml)
name: 🐳 Docker (Multi-Arch)

on:
  workflow_dispatch: {}
  pull_request:
    branches: [ "main" ]
  push:
    branches: [ "main" ]
    tags: [ "*" ]

env:
  REGISTRY: ghcr.io
  IMAGE_NAME: ${{ github.repository }}

jobs:
  build:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      packages: write
      id-token: write

    steps:
      - name: πŸ“₯ Checkout repository
        uses: actions/checkout@v4

      - name: 🐹 Set up Go
        uses: actions/setup-go@v4
        with:
          go-version: '1.20'
       
      - name: 🧱 Build binaries
        run: |
          GOOS=linux GOARCH=amd64 CGO_ENABLED=0 go build -o linux_amd64
          GOOS=linux GOARCH=arm64 CGO_ENABLED=0 go build -o linux_arm64

      - name: πŸ› οΈ Set up Docker Buildx
        uses: docker/setup-buildx-action@v3
        with:
          driver: docker-container
          install: true
          use: true

      - name: πŸ” Log into registry ${{ env.REGISTRY }}
        if: github.event_name != 'pull_request'
        uses: docker/login-action@v3
        with:
          registry: ${{ env.REGISTRY }}
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}

      - name: 🏷️ Extract Docker metadata
        id: meta
        uses: docker/metadata-action@v5
        with:
          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
          tags: |
            type=raw,value=latest,enable={{is_default_branch}}
            type=semver,pattern={{version}}
            type=ref,event=branch
            type=ref,event=tag
            type=ref,event=pr

      - name: πŸš€ Build and push Docker image (Multi-Arch)
        id: build-and-push
        uses: docker/build-push-action@v5
        with:
          context: .
          file: Dockerfile.ghcr
          push: ${{ github.event_name != 'pull_request' }}
          tags: ${{ steps.meta.outputs.tags }}
          labels: ${{ steps.meta.outputs.labels }}
          platforms: linux/amd64,linux/arm64
          provenance: false
          cache-from: type=gha
          cache-to: type=gha,mode=max

The same workflow, on Latchkey

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

name: 🐳 Docker (Multi-Arch)
 
on:
  workflow_dispatch: {}
  pull_request:
    branches: [ "main" ]
  push:
    branches: [ "main" ]
    tags: [ "*" ]
 
env:
  REGISTRY: ghcr.io
  IMAGE_NAME: ${{ github.repository }}
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build:
    timeout-minutes: 30
    runs-on: latchkey-small
    permissions:
      contents: read
      packages: write
      id-token: write
 
    steps:
      - name: πŸ“₯ Checkout repository
        uses: actions/checkout@v4
 
      - name: 🐹 Set up Go
        uses: actions/setup-go@v4
        with:
          go-version: '1.20'
       
      - name: 🧱 Build binaries
        run: |
          GOOS=linux GOARCH=amd64 CGO_ENABLED=0 go build -o linux_amd64
          GOOS=linux GOARCH=arm64 CGO_ENABLED=0 go build -o linux_arm64
 
      - name: πŸ› οΈ Set up Docker Buildx
        uses: docker/setup-buildx-action@v3
        with:
          driver: docker-container
          install: true
          use: true
 
      - name: πŸ” Log into registry ${{ env.REGISTRY }}
        if: github.event_name != 'pull_request'
        uses: docker/login-action@v3
        with:
          registry: ${{ env.REGISTRY }}
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}
 
      - name: 🏷️ Extract Docker metadata
        id: meta
        uses: docker/metadata-action@v5
        with:
          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
          tags: |
            type=raw,value=latest,enable={{is_default_branch}}
            type=semver,pattern={{version}}
            type=ref,event=branch
            type=ref,event=tag
            type=ref,event=pr
 
      - name: πŸš€ Build and push Docker image (Multi-Arch)
        id: build-and-push
        uses: docker/build-push-action@v5
        with:
          context: .
          file: Dockerfile.ghcr
          push: ${{ github.event_name != 'pull_request' }}
          tags: ${{ steps.meta.outputs.tags }}
          labels: ${{ steps.meta.outputs.labels }}
          platforms: linux/amd64,linux/arm64
          provenance: false
          cache-from: type=gha
          cache-to: type=gha,mode=max
 

What changed

4 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:

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