Regolith Deb Builder

This is a container to build Regolith packages for all supported distros and codenames on GitHub Actions. It contains all the necessary files and dependencies for voulage and actions and their corresponding scripts to work.

It supports building containers for multiple versions of Ubuntu and Debian (e.g. LTS releases and the "latest" release) by specifying them as build arguments for the Docker container build process:

$ docker build --build-arg=REFERENCE="ubuntu:<ubuntu-version>" -t ci-ubuntu:<ubuntu-version> .

For example, to build a container for "Focal Fossa":

$ docker build --build-arg=REFERENCE="ubuntu:focal" -t ci-ubuntu:focal .

The GitHub Actions for this repository are set up to build all supported releases in a matrix and push them to GitHub Packages for the consumption in other GitHub Actions from other repositories.

Supported Container Registry

The images are pushed to GitHub Container Registry and are accessible under regolith-linux namespace.

Supported Tags

Debian

The supported releases of Debian for different CPU architecture.

Image Name	Tag Name (amd64)	Tag Name (arm64)	End of Life
ci-debian	bullseye-amd64	bullseye-arm64	✔
ci-debian	bookworm-amd64	bookworm-arm64	-
ci-debian	trixie-amd64	trixie-arm64	-
ci-debian	testing-amd64	testing-arm64	-

Ubuntu

The supported releases of Ubuntu for different CPU architecture.

Image Name	Tag Name (amd64)	Tag Name (arm64)	End of Life
ci-ubuntu	focal-amd64	focal-arm64	✔
ci-ubuntu	jammy-amd64	jammy-arm64	-
ci-ubuntu	kinetic-amd64	kinetic-arm64	✔
ci-ubuntu	lunar-amd64	lunar-arm64	✔
ci-ubuntu	mantic-amd64	mantic-arm64	✔
ci-ubuntu	noble-amd64	noble-arm64	-
ci-ubuntu	oracular-amd64	oracular-arm64	✔
ci-ubuntu	plucky-amd64	plucky-arm64	-
ci-ubuntu	questing-amd64	questing-arm64	-

Example

docker pull ghcr.io/regolith-linux/ci-debian:bookworm-arm64

Add new Distro or Codename

Make sure the new distro or codename being added exists in voulage's unstable stage and then run Generate Distro Folders actions. This will create the corresponding folder and pushe the changes back to the main branch.

You may want to adjust additional-packages content for this new distro and/or codename in a separate pull request. And add a new entry in the corresponding table in Supported Tags section above.