Pre-built Docker images for wolfBoot GitHub Actions CI, eliminating per-run toolchain downloads and apt-get overhead.
All images use Devuan testing as the base (except renode).
| Image | Purpose | Base |
|---|---|---|
wolfboot-ci-base |
Shared foundation: build-essential, cmake, ninja, python3, libwolfssl-dev | devuan:testing |
wolfboot-ci-arm |
ARM cross-compilation: arm-none-eabi-gcc, aarch64-linux-gnu, clang | base |
wolfboot-ci-powerpc |
PowerPC cross-compilation: powerpc-linux-gnu-gcc | base |
wolfboot-ci-sim |
Host simulator tests: 32-bit libc, libcheck | base |
wolfboot-ci-m33mu |
TrustZone emulator tests: ARM toolchain + m33mu + MCUXpresso SDK | devuan:testing |
wolfboot-ci-riscv |
RISC-V: xPack GCC + freedom-e-sdk | base |
wolfboot-ci-aarch64 |
Bare-metal AArch64: aarch64-none-elf toolchain | base |
wolfboot-ci-x86 |
x86 QEMU: nasm, gcc-multilib, qemu-system-x86, swtpm | base |
wolfboot-ci-renode |
Renode emulation: renode + arm-none-eabi-gcc | antmicro/renode |
Tag the base with its full image name so derived builds find the local image.
# Build base first
podman build --no-cache -t ghcr.io/wolfssl/wolfboot-ci-base:testing base/
# Build derived images (replace 'arm' with any image name)
podman build --no-cache --build-arg BASE_TAG=testing -t wolfboot-ci-arm:testing arm/
# Build m33mu image
podman build --no-cache -t wolfboot-ci-m33mu:testing m33mu/wolfBoot's NXP targets need a west-provisioned MCUXpresso SDK tree and NXP's
CMSIS_5 fork; without them a build stops at fsl_common.h: No such file or directory. The m33mu image ships both, and exports
MCUXPRESSO=/opt/nxp/mcuxpresso-sdk/mcuxsdk
MCUXPRESSO_CMSIS=/opt/nxp/CMSIS_5/CMSIS
wolfBoot's example configs set these with ?=, so the environment wins and
jobs need no extra make arguments. Plain make works.
Only the west projects behind the paths wolfBoot's makefiles name are fetched
(core, CMSIS, components, examples, the LPC, MCX, RT and Wireless device trees,
els_pkc and secure-subsystem).
Use MCUX_PROJECTS to extend this set; MCUX_BOARDS is no longer used.
The NXP board manifests also pull TF-M, eIQ and other middleware whose GitLab
submodules break the build whenever GitLab is overloaded, so the image skips
them:
# Add a device family (for example Kinetis)
podman build --no-cache \
--build-arg MCUX_PROJECTS="core CMSIS mcu-sdk-components mcu-sdk-examples mcux-devices-lpc mcux-devices-mcx mcux-devices-rt mcux-devices-wireless els_pkc secure-subsystem mcux-devices-kinetis" \
-t wolfboot-ci-m33mu:testing m33mu/
# Keep every example instead of only examples/_boards
podman build --no-cache --build-arg MCUX_PRUNE=0 -t wolfboot-ci-m33mu:testing m33mu/jobs:
build:
runs-on: ubuntu-latest
container:
image: ghcr.io/wolfssl/wolfboot-ci-arm:latest
steps:
- uses: actions/checkout@v4
with:
submodules: true
- name: Init submodules
run: |
git config --global --add safe.directory "$GITHUB_WORKSPACE"
git submodule update --init --single-branch
- name: Build
run: makePull requests build each changed image without publishing it. Changes to base/
also build its dependent images. Each dependent image builds against the base
Dockerfile in the pull request, so changes to both are tested together.
Pushes to master, including merged pull requests, build and publish all images
to GHCR with the master and latest tags. Pull request checks build images
without publishing them.
Version tag pushes also publish images with the version tag and latest:
git tag v1.0
git push origin v1.0Individual images can also be built via workflow dispatch.