Skip to content
Latchkey

Build and Publish Multi-Arch Docker Image workflow (Autonomy-Logic/openplc-runtime)

The Build and Publish Multi-Arch Docker Image workflow from Autonomy-Logic/openplc-runtime, 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: Autonomy-Logic/openplc-runtime.github/workflows/docker.ymlLicense MITView source

What it does

This is the Build and Publish Multi-Arch Docker Image workflow from the Autonomy-Logic/openplc-runtime 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

workflow (.yml)
name: Build and Publish Multi-Arch Docker Image

on:
  push:
    tags:
      - 'v*'
  workflow_dispatch:
    inputs:
      platforms:
        description: 'Platforms to build (comma-separated)'
        default: 'linux/amd64,linux/arm64,linux/arm/v7'
        required: false
        type: string
      release_tag:
        description: 'Release version tag (e.g., 1.2.3). If provided, also tags as latest.'
        required: false
        type: string

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

    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Set up QEMU
        uses: docker/setup-qemu-action@v3

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

      - name: Login to GHCR
        uses: docker/login-action@v3
        with:
          registry: ghcr.io
          username: ${{ secrets.GHCR_USERNAME }}
          password: ${{ secrets.GHCR_TOKEN }}

      - name: Extract Docker metadata
        id: meta
        uses: docker/metadata-action@v5
        with:
          images: ghcr.io/autonomy-logic/openplc-runtime
          tags: |
            # latest tag only for stable releases (no pre-release suffix like -rc, -beta, etc.)
            type=raw,value=latest,enable=${{ (startsWith(github.ref, 'refs/tags/v') && !contains(github.ref, '-')) || inputs.release_tag != '' }}
            # Version tag from git tag (e.g., v1.2.3 -> v1.2.3, v1.2.3-rc.1 -> v1.2.3-rc.1)
            type=semver,pattern={{raw}}
            # Version tag for manual runs with release_tag
            type=raw,value=${{ inputs.release_tag }},enable=${{ inputs.release_tag != '' }}

      - name: Build and Push Multi-Arch Image
        uses: docker/build-push-action@v6
        with:
          context: .
          push: true
          platforms: ${{ inputs.platforms || 'linux/amd64,linux/arm64,linux/arm/v7' }}
          tags: ${{ steps.meta.outputs.tags }}
          labels: ${{ steps.meta.outputs.labels }}
          # Bake the GitHub release tag (or the workflow_dispatch
          # release_tag override) into the image so /api/version can
          # report it back to clients.  Falls back to the Dockerfile
          # default ("dev") for ad-hoc builds without a release tag.
          build-args: |
            RUNTIME_VERSION=${{ inputs.release_tag != '' && inputs.release_tag || github.ref_name }}

The same workflow, on Latchkey

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

name: Build and Publish Multi-Arch Docker Image
 
on:
  push:
    tags:
      - 'v*'
  workflow_dispatch:
    inputs:
      platforms:
        description: 'Platforms to build (comma-separated)'
        default: 'linux/amd64,linux/arm64,linux/arm/v7'
        required: false
        type: string
      release_tag:
        description: 'Release version tag (e.g., 1.2.3). If provided, also tags as latest.'
        required: false
        type: string
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build:
    timeout-minutes: 30
    runs-on: latchkey-small
    permissions:
      contents: read
      packages: write
 
    steps:
      - name: Checkout
        uses: actions/checkout@v4
 
      - name: Set up QEMU
        uses: docker/setup-qemu-action@v3
 
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v3
 
      - name: Login to GHCR
        uses: docker/login-action@v3
        with:
          registry: ghcr.io
          username: ${{ secrets.GHCR_USERNAME }}
          password: ${{ secrets.GHCR_TOKEN }}
 
      - name: Extract Docker metadata
        id: meta
        uses: docker/metadata-action@v5
        with:
          images: ghcr.io/autonomy-logic/openplc-runtime
          tags: |
            # latest tag only for stable releases (no pre-release suffix like -rc, -beta, etc.)
            type=raw,value=latest,enable=${{ (startsWith(github.ref, 'refs/tags/v') && !contains(github.ref, '-')) || inputs.release_tag != '' }}
            # Version tag from git tag (e.g., v1.2.3 -> v1.2.3, v1.2.3-rc.1 -> v1.2.3-rc.1)
            type=semver,pattern={{raw}}
            # Version tag for manual runs with release_tag
            type=raw,value=${{ inputs.release_tag }},enable=${{ inputs.release_tag != '' }}
 
      - name: Build and Push Multi-Arch Image
        uses: docker/build-push-action@v6
        with:
          context: .
          push: true
          platforms: ${{ inputs.platforms || 'linux/amd64,linux/arm64,linux/arm/v7' }}
          tags: ${{ steps.meta.outputs.tags }}
          labels: ${{ steps.meta.outputs.labels }}
          # Bake the GitHub release tag (or the workflow_dispatch
          # release_tag override) into the image so /api/version can
          # report it back to clients.  Falls back to the Dockerfile
          # default ("dev") for ad-hoc builds without a release tag.
          build-args: |
            RUNTIME_VERSION=${{ inputs.release_tag != '' && inputs.release_tag || github.ref_name }}
 

What changed

5 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