Skip to content

Prepare for building multiple containers #3

Prepare for building multiple containers

Prepare for building multiple containers #3

#
name: Build and publish whisper docker image
# Configures this workflow to run every time a change is pushed to the branch called `release`.
on:
workflow_dispatch:
push:
paths:
- '../../containers/*'
- '.github/workflows/build-publish-containers.yml'
# Defines two custom environment variables for the workflow. These are used for the Container registry domain, and a name for the Docker image that this workflow builds.
env:
IMAGE_NAME: ${{ github.repository }}
MEDIA_DOWNLOAD_IMAGE_NAME: ${{ github.repository }}_media-download
BUILD_NUMBER: ${{ github.run_number }}
GITHUB_REGISTRY: ghcr.io
# There is a single job in this workflow. It's configured to run on the latest available version of Ubuntu.
jobs:
build-and-push-image:
runs-on: ubuntu-latest
# Sets the permissions granted to the `GITHUB_TOKEN` for the actions in this job.
permissions:
contents: read
packages: write
id-token: write
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
# Uses the `docker/login-action` action to log in to the Container registry using the account and password that will publish the packages. Once published, the packages are scoped to the account defined here.
- name: Log in to the Container registry
uses: docker/login-action@v3
with:
registry: ${{ env.GITHUB_REGISTRY }}
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
# This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) to extract tags and labels that will be applied to the specified image. The `id` "meta" allows the output of this step to be referenced in a subsequent step. The `images` value provides the base name for the tags and labels.
# Note - this step is the thing where we are indicating which repositories we want to push the container to
- name: Extract metadata (tags, labels) for Docker
id: meta
uses: docker/metadata-action@v5
with:
tags: |
type=sha
type=raw,value=latest
- uses: aws-actions/configure-aws-credentials@v4
name: Configure AWS credentials for pushing to ECR
with:
role-to-assume: ${{ secrets.INVESTIGATIONS_GITHUB_ACTIONS_ROLE_ARN }}
aws-region: eu-west-1
- name: Login to Amazon ECR
id: login-ecr
uses: aws-actions/amazon-ecr-login@v2
# This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to GitHub Packages.
# It uses the `context` parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the `docker/build-push-action` repository.
# It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step.
- name: Build and push whisper Docker image
uses: docker/build-push-action@v5
with:
file: containers/whisper.Dockerfile
# to add x86: linux/amd64
platforms: linux/arm64
push: true
tags:
- ${{ steps.meta.outputs.tags }}

Check failure on line 70 in .github/workflows/build-publish-containers.yml

View workflow run for this annotation

GitHub Actions / Build and publish whisper docker image

Invalid workflow file

The workflow is not valid. .github/workflows/build-publish-containers.yml (Line: 70, Col: 13): A sequence was not expected
- ${{ env.GITHUB_REGISTRY }}/${{ env.IMAGE_NAME }}
- ${{ secrets.TRANSCRIPTION_SERVICE_ECR_URI }}
labels: ${{ steps.meta.outputs.labels }}
cache-from: type=gha
cache-to: type=gha,mode=max