Shared workflow for Docker build and push

Reusable GitHub workflow for building, scanning and pushing a Docker image to a container registry.

Usage

jobs:
  build-push:
    uses: nrkno/github-workflow-docker-build-push/.github/workflows/[email protected]
    with:
      runs-on: "['self-hosted', 'linux']"
      registry-url: myregistry.azurecr.io
      name: my-project-name/my-image-name
      # Tag with 'latest' tag when merging to main
      tag-latest: ${{ github.ref == 'refs/heads/main' }}
      # Only push when merging to main
      push: ${{ github.ref == 'refs/heads/main' }}
    secrets:
      registry-username: secret-string
      registry-password: secret-string
      token: ${{ secrets.GITHUB_TOKEN }}

Inputs

• cache (boolean, default true) - Whether to enable image layer cache.
• cache-tag (string, default "buildcache") - Image tag to use for image layer cache.
• context (string, default ".") - The root directory for the Docker build context.
• dockerfile (string, default "Dockerfile") - Path to a Dockerfile relative to the Docker build context path.
• git-ref (string, default "") - The branch, tag or SHA to checkout. Leave empty for the current branch ref.
• git-submodules (boolean, default false) - Whether to also checkout Git submodules.
• push (boolean, default true) - Push a successfully built image to a registry.
• name (string, required) - Image name (repository path) within a registry.
• tag-branch (boolean, default false) - Tag a successfully built image with the branch name.
• tag-sha (boolean, default true) - Tag a successfully built image with the commit SHA that triggered the workflow.
• tag-pr (boolean, default true) - Tag a successfully built image with reference to a Pull Request, e.g. pr-2.
• tag-latest (boolean, default false) - Tag a successfully built image with the tag latest.
• tag-extra (string, default "") - Comma-separated list of additional image tags.
• registry-url (string, required) - URL to the container registry.
• runs-on (string, default "['self-hosted']") - Type of runner for the jobs. For non-self-hosted runners, use ubuntu-latest for example.
• trivy-enabled (boolean, default true) - Scan the built image for known vulnerabilities using Trivy.
• trivy-error-is-success (boolean, default false) - Do not produce an error if the Trivy scan fails. Primarily used for testing.
• trivy-ignore-unfixed (boolean, default true) - Ignore errors that do not have a known fix.
• trivy-ignore-files (string, default "") - Comma-separated list of paths to Trivy ignore files, relative to the repository root.
• trivy-severity (string, default "MEDIUM,HIGH,CRITICAL") - Comma-separated list of severities to consider an error.
• trivy-summary-enabled (boolean, default false) - Render a table of all the Trivy findings in the GitHub summary for the workflow.
• trivy-sbom-enabled (boolean, default false) - Generate an SBOM of your dependencies and submit them to GitHub Dependency Graph.

Secrets

• git-ssh-key - SSH key used by Git to checkout the repository.
• registry-username (required) - Username for the container registry.
• registry-password (required) - Password for the container registry.
• token (required) - GitHub auth token.

Outputs

• image-digest - The image digest for this build.
• image-ref - An image reference for this build (<name>:<git-sha>@<digest>).
• image-ref-stripped - An image reference for this build, stripped of its registry URL (<name>:<git-sha>@<digest>).
• image-tags - Comma-separated list of generated image tags for this build, (<registry-url>/<name1>:<tag1>,<registry-url>/<name1>:<tag2>).
• image-tags-stripped - Comma-separated list of generated image tags for this build, stripped of their registry URL, without a leading slash (<name1>:<tag1>,<name1>:<tag2>).
• unique-id - A generated unique ID for this run. Can be useful when debugging runners to determine artifact filenames.

Implementation notes

The build, scan and push phases have been merged into one job to simplify workflow runs. This degrades the visualisation of the pipeline, but the save in speed and maintenance is significant. To separate the steps it is necessary to cache the built image between jobs, causing a lot of time spent uploading and downloading artifacts.

The registry URL must be passed as a secret when it's sourced from a repository secret. This prevents us from printing the full image refs in the workflow outputs and job summary. This has been worked around by outputting tags stripped of their registry URLs.

References

• https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_callinputs
• https://docs.github.com/en/actions/using-workflows/reusing-workflows
• https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary