DVSA Images

Docker Images for use in DVSA projects. The images are re-built weekly to pull in the latest patches and updates.

How to use

FROM ghcr.io/dvsa/dvsa-docker-images/php/8.3/fpm-nginx:0.6.0

Tip

Different specifity levels can be used to pin the image version. The most specific is the git-sha which is the most immutable. The least specific is latest which is the most mutable. See the tagging strategy for more information.

Reccommended image hierarchy

block-beta
    block:image
        columns 1
        label["Application"]
        linux["Linux image (Alpine, Ubuntu, etc)"]
        language["Language image (Node, PHP, etc)"]
        base["DVSA image (php/8.3/fpm-nginx, php/8.3/cli, etc)"]
        project["Project-specific Image"]
        style label fill:transparent,stroke:0,stroke-width:0
    end

Loading

Tagging strategy

The Docker images are tagged during the CD pipeline (running on push to main and on a schedule) with the following tags:

gitGraph
    commit id: "[git-sha1]"
    commit tag: "v1.0.0" id: "1.0.0, 1.0, 1, [git-sha2]"
    commit id: "[git-sha3]"
    commit id: "[git-sha4]"
    commit tag: "v1.1.0" id: "1.1.0, 1.1, 1, [git-sha5]"
    commit tag: "v1.1.1" id: "1.1.1, 1.1, 1, [git-sha6]"
    commit id: "[git-sha7]"
    commit id: "[git-sha8]"
    commit tag: "v1.2.0" id: "1.2.0, 1.2, 1, [git-sha9]"
    commit id: "[git-sha10], latest"

Loading

Warning

Mutable tags: latest, [major].[minor], & [major].
Immutable tags: [major].[minor].[patch], & [git-sha].

Mutable tags are updated on push and schedule. [git-sha] are updated on every commit. [major].[minor].[patch] are updated on every release.

Adding a new base image

Note

This repository is for generic base images. Do not add project-specific images here. Project-specific images should be added to the project repository.

1. Create a new directory in the root of this repository with the name of the image you want to create. The convention is usually [language]/[version]/[flavour] e.g. node/12/alpine, php/8.3/fpm-nginx etc.

2. Create a Dockerfile in the directory you just created. This file should contain the instructions for building the image.

3. Update the docker job in ci.yaml and cd.yaml and update the matrix to add your new image. This ensures the image is build & pushed if it has changed (or during a new release).

   strategy:
     fail-fast: false
     matrix:
       base:
         # ...
         - node/20/alpine
       exclude:
         # ...
         - base: ${{ github.event_name == 'schedule' || needs.release-please.outputs.release_created || contains(needs.orchestrator.outputs.changed-directories, 'node/20/alpine') && 'ignored' || 'node/20/alpine' }}