- Shell 100%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
install-toolset.sh vendors and runs the actual install-*.sh scripts and toolset.json manifest from actions/runner-images at a pinned tag, for closer parity with a real GitHub ubuntu-24.04 runner. install-runner.sh now only installs the Forgejo runner itself. Also fixes what's needed to make those vendored scripts work on this image's minimal debootstrap base rather than the full Ubuntu cloud image they assume: apt components/sources, lsb-release, software-properties-common, locale generation, an unresolvable virtual apt package, and a real bug where invoking each script via `bash file` instead of `bash -e file` silently discarded its own `set -e`. Also resolves the literal "$HOME/..." PATH entries the toolset writes to /etc/environment for the "runner" user, which upstream itself only fixes via a manual post-boot step (see https://github.com/actions/runner-images/issues/3695). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Da7DdtiE7PpFxjnUhN4eNW |
||
| .envrc | ||
| .gitignore | ||
| docker.inc.yaml | ||
| forgejo-runner-ubuntu.yaml | ||
| install-runner.sh | ||
| install-toolset.sh | ||
| README.md | ||
A Proxmox VM Template for a Full-Fledged Forgejo Runner
This repo uses PVE Template Builder to build a Proxmox VM Template that contains the Forgejo Runner as well as many common tools. The goal is to have a runner that is (mostly) compatible with a GitHub ubuntu24.04 runner.
install-toolset.sh installs the tool set by fetching the actual install-*.sh scripts and toolset.json manifest from actions/runner-images at a pinned tag and running them directly, instead of reimplementing them. This intentionally leaves out the pieces of the upstream Packer build that are Azure- or GitHub Actions-specific (VM deprovisioning, the PowerShell-driven multi-version language toolcache, MS package repos, software report/test generation); see the comments in install-toolset.sh for the full list. Bumping RUNNER_IMAGES_REF in that script is all that's needed to pick up a newer upstream toolset — no fork required.