Lucas Schwiderski
1c51336727
All checks were successful
/ build (push) Successful in 12s
Reviewed-on: #7 |
||
|---|---|---|
| .forgejo/workflows | ||
| examples | ||
| scripts | ||
| .dockerignore | ||
| .gitignore | ||
| .renovaterc | ||
| Dockerfile | ||
| Justfile | ||
| LICENSE | ||
| README.md | ||
forgejo-actions-buildkit-image
A Docker image for the Forgejo Runner containing client tools for BuildKit and Docker.
Tools required for basic operations in Forgejo Actions, such a nodejs, git and zstd
(for actions/cache) are also included.
The intended use for this image is to be registered as a label in a runner, like
buildkit:docker://git.sclu1034.dev/lucas/forgejo-actions-buildkit-image:latest. A runner with this label would then be
expected to provide access to a BuildKit daemon and a Docker daemon to the job container.
Please check out the examples/.
Version number
The versioned tags follow the BuildKit version. A revision number may be added if necessary.
Development
Building the image locally with just Docker works as usual.
The Forgejo Actions workflows utilize BuildKit to build the image, and Docker to test the image. A runner needs the to be setup with this image as outlined above.
For running the workflows locally, the runner already injects the local Docker daemon socket, and the
script scripts/forgejo-runner-exec wraps the forgejo-runner exec call to provide a BuildKit daemon.