Build & Push Docker Image workflow (vanvalenlab/deepcell-tf)
The Build & Push Docker Image workflow from vanvalenlab/deepcell-tf, explained and optimized by Latchkey.
CI health: B - good
Point runs-on at Latchkey and get job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Build & Push Docker Image workflow from the vanvalenlab/deepcell-tf 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
name: Build & Push Docker Image
on:
release:
types: [published]
jobs:
docker:
runs-on: ubuntu-latest
env:
TF_VERSION: 2.8.0
steps:
- 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 DockerHub
uses: docker/login-action@v3
with:
username: ${{ secrets.DOCKER_USERNAME }}
password: ${{ secrets.DOCKER_PASSWORD }}
- name: Build and push CPU Image
id: docker_build_cpu
uses: docker/build-push-action@v5
with:
context: .
file: ./Dockerfile
push: true
tags: |
${{ github.repository }}:latest
${{ github.repository }}:${{ github.event.release.tag_name }}
build-args: |
TF_VERSION=${{ env.TF_VERSION }}
- name: Image digest
run: echo ${{ steps.docker_build_cpu.outputs.digest }}
- name: Build and push GPU Image
id: docker_build_gpu
uses: docker/build-push-action@v5
with:
context: .
file: ./Dockerfile
push: true
tags: |
${{ github.repository }}:latest-gpu
${{ github.repository }}:${{ github.event.release.tag_name }}-gpu
build-args: |
TF_VERSION=${{ env.TF_VERSION }}-gpu
- name: Image digest
run: echo ${{ steps.docker_build_gpu.outputs.digest }}
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Build & Push Docker Image on: release: types: [published] jobs: docker: timeout-minutes: 30 runs-on: latchkey-small env: TF_VERSION: 2.8.0 steps: - 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 DockerHub uses: docker/login-action@v3 with: username: ${{ secrets.DOCKER_USERNAME }} password: ${{ secrets.DOCKER_PASSWORD }} - name: Build and push CPU Image id: docker_build_cpu uses: docker/build-push-action@v5 with: context: . file: ./Dockerfile push: true tags: | ${{ github.repository }}:latest ${{ github.repository }}:${{ github.event.release.tag_name }} build-args: | TF_VERSION=${{ env.TF_VERSION }} - name: Image digest run: echo ${{ steps.docker_build_cpu.outputs.digest }} - name: Build and push GPU Image id: docker_build_gpu uses: docker/build-push-action@v5 with: context: . file: ./Dockerfile push: true tags: | ${{ github.repository }}:latest-gpu ${{ github.repository }}:${{ github.event.release.tag_name }}-gpu build-args: | TF_VERSION=${{ env.TF_VERSION }}-gpu - name: Image digest run: echo ${{ steps.docker_build_gpu.outputs.digest }}
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 useslatchkey-small; pick the runner size that fits the job. - Add a job timeout so a hung step cannot burn hours of runner time.
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:
- 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.