- Shell 52.8%
- Dockerfile 25.2%
- Just 22%
|
All checks were successful
/ check (pull_request) Successful in 13s
Reviewed-on: #5 |
||
|---|---|---|
| .forgejo/workflows | ||
| examples | ||
| scripts | ||
| .dockerignore | ||
| .gitignore | ||
| .renovaterc | ||
| Dockerfile | ||
| Justfile | ||
| LICENSE | ||
| README.md | ||
forgejo-actions-cross-image
A Docker image for the Forgejo Runner providing the Rust cross-compiler cross.
Tools required for basic operations in Forgejo Actions, such a nodejs, git and zstd
(for actions/cache) are also included.
The image may be configured as a Runner label, or set manually in a workflow with
container.image: git.sclu1034.dev/lucas/forgejo-actions-cross-image:latest.
The workflow needs access to a Docker daemon, and you'll need to set CROSS_REMOTE=1 or
CROSS_CONTAINER_IN_CONTAINER=1 depending on the exact setup.
Please check out the examples/.
Version number
The versioned tags follow the cross 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 to be set up with https://git.sclu1034.dev/lucas/forgejo-actions-buildkit-image.
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.