Publish to DockerHub workflow (mead-ml/mead-baseline)

The Publish to DockerHub workflow from mead-ml/mead-baseline, explained and optimized by Latchkey.

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: mead-ml/mead-baseline.github/workflows/dockerhub.ymlLicense Apache-2.0View source

What it does

This is the Publish to DockerHub workflow from the mead-ml/mead-baseline 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: Publish to DockerHub 

on:
    push:
        branches:
        - 'master'

jobs:
    build:
        runs-on: ubuntu-latest
        steps:
        - name: Checkout
          uses: actions/checkout@v2
        - name: Set up Docker Buildx
          uses: docker/setup-buildx-action@v1
        - name: Login to DockerHub
          uses: docker/login-action@v1
          with:
              username: ${{ secrets.DOCKER_USERNAME }}
              password: ${{ secrets.DOCKER_PASSWORD }}
        - name: Build & Push PyTorch CUDA 10 image
          uses: docker/build-push-action@v2
          with:
              file: docker/Dockerfile.pytorch-cuda10 
              push: true
              tags: meadml/mead2-pytorch-gpu:latest
        - name: Build & Push PyTorch CUDA 11 image
          uses: docker/build-push-action@v2
          with:
              file: docker/Dockerfile.pytorch-cuda11
              push: true
              tags: meadml/mead2-pytorch-cuda11:latest
        - name: Build & Push PyTorch CUDA 11.1 image
          uses: docker/build-push-action@v2
          with:
              file: docker/Dockerfile.pytorch-cuda111
              push: true
              tags: meadml/mead2-pytorch-cuda111:latest
        - name: Build & Push PyTorch CUDA 11 ext image
          uses: docker/build-push-action@v2
          with:
              file: docker/Dockerfile.pytorch-cuda11x
              push: true
              tags: meadml/mead2-pytorch-cuda11x:latest
        - name: Build & Push PyTorch CUDA 11.1 ext image
          uses: docker/build-push-action@v2
          with:
              file: docker/Dockerfile.pytorch-cuda111x
              push: true
              tags: meadml/mead2-pytorch-cuda111x:latest
        - name: Build & Push TF2 CUDA 10 image
          uses: docker/build-push-action@v2
          with:
              file: docker/Dockerfile.tf2-cuda10 
              push: true
              tags: meadml/mead2-tf2-gpu:latest
        - name: Build & Push TF2 CUDA 11 image
          uses: docker/build-push-action@v2
          with:
              file: docker/Dockerfile.tf2-cuda11
              push: true
              tags: meadml/mead2-tf2-cuda11:latest

The same workflow, on Latchkey

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

name: Publish to DockerHub 
 
on:
    push:
        branches:
        - 'master'
 
concurrency:
    group: ${{ github.workflow }}-${{ github.ref }}
    cancel-in-progress: true
 
jobs:
    build:
        timeout-minutes: 30
        runs-on: latchkey-small
        steps:
        - name: Checkout
          uses: actions/checkout@v2
        - name: Set up Docker Buildx
          uses: docker/setup-buildx-action@v1
        - name: Login to DockerHub
          uses: docker/login-action@v1
          with:
              username: ${{ secrets.DOCKER_USERNAME }}
              password: ${{ secrets.DOCKER_PASSWORD }}
        - name: Build & Push PyTorch CUDA 10 image
          uses: docker/build-push-action@v2
          with:
              file: docker/Dockerfile.pytorch-cuda10 
              push: true
              tags: meadml/mead2-pytorch-gpu:latest
        - name: Build & Push PyTorch CUDA 11 image
          uses: docker/build-push-action@v2
          with:
              file: docker/Dockerfile.pytorch-cuda11
              push: true
              tags: meadml/mead2-pytorch-cuda11:latest
        - name: Build & Push PyTorch CUDA 11.1 image
          uses: docker/build-push-action@v2
          with:
              file: docker/Dockerfile.pytorch-cuda111
              push: true
              tags: meadml/mead2-pytorch-cuda111:latest
        - name: Build & Push PyTorch CUDA 11 ext image
          uses: docker/build-push-action@v2
          with:
              file: docker/Dockerfile.pytorch-cuda11x
              push: true
              tags: meadml/mead2-pytorch-cuda11x:latest
        - name: Build & Push PyTorch CUDA 11.1 ext image
          uses: docker/build-push-action@v2
          with:
              file: docker/Dockerfile.pytorch-cuda111x
              push: true
              tags: meadml/mead2-pytorch-cuda111x:latest
        - name: Build & Push TF2 CUDA 10 image
          uses: docker/build-push-action@v2
          with:
              file: docker/Dockerfile.tf2-cuda10 
              push: true
              tags: meadml/mead2-tf2-gpu:latest
        - name: Build & Push TF2 CUDA 11 image
          uses: docker/build-push-action@v2
          with:
              file: docker/Dockerfile.tf2-cuda11
              push: true
              tags: meadml/mead2-tf2-cuda11:latest

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

actions/checkout docker/setup-buildx-action docker/login-action docker/build-push-action