The builder of the RTE images an AnsibleForms controller defines, written in Node.js. It joins the controller, builds each image the Designer asks for with BuildKit, and pushes it to its registry.
docker run -d --name af-builder \
--security-opt seccomp=unconfined --security-opt apparmor=unconfined \
-e CONTROLLER_URL=https://forms.example.com -e RTE_TOKEN=<at least 16 characters> \
-e RTE_JOIN_TOKEN=<a join token from the Designer's RTE builders> \
-v af-builder:/home/node/work ghcr.io/ansibleforms/ansibleforms-rte-builderThe controller decides what to build; the builder builds it, and knows nothing else.
- Joins like a Runner: dials the controller, with a join token or an admin's approval
- Builds with BuildKit: a rootless buildkitd of its own, or the one
BUILDKIT_HOSTnames - Pushes to any registry: the login comes sealed with each build and is never kept
- Signs and lists: cosign signatures, offline, and an SBOM pushed with the image
- Live log: every line of a build reaches the controller's job, its secrets masked
- Survives a drop: what the controller did not store yet is sent again after a reconnect
- Needs nothing more: no database, no repositories, no playbooks
The RTE images are defined in the controller's Designer, which writes each one's Dockerfile. A build is a job: the controller hands it to a builder that is online, with the Dockerfile, the reference to push to, and the registry login and signing key sealed for that builder; the build's log and result come back as the job's.
The builder and the controller meet over the controller's runner socket, at a version of its contract. A builder works with every controller that speaks the same contract, whatever their releases.
Each AnsibleForms release publishes ansibleforms-rte-builder at the same version, for amd64 and arm64.
A builder needs a controller with RTE images (AnsibleForms 7.8.0 and later); CHANGELOG.md lists its own changes.
Contributions are welcome. Start with these files:
- CONTRIBUTING.md: how to build and test it, the socket contract, and how it is released
- CHANGELOG.md: the changes in every release
- SECURITY.md: how to report a security issue