Updated in homelab: forgejo-runner-rust now uses docker:27-cli image
which includes Node.js + git + docker + full dev tools.
This allows actions/checkout@v4 and other GitHub Actions to work.
Workflow simplified:
- No container override (use runner's native environment)
- Uses actions/checkout@v4 (requires Node.js)
- Builds and pushes to registry
Test commit to verify new runner configuration works.
The rust runner pod is pre-configured with:
- Rust 1.83-bookworm base image
- Docker CLI + Node.js (for GitHub Actions)
- Git + all build tools
- TLS-secured docker daemon connection at tcp://localhost:2376
Don't override with a container image. Use the runner's native environment.
This is the correct pattern for self-hosted runners.
Previous issue: git repo check at /workspace/rock failed
Solution:
- Clone repo explicitly into /src directory
- cd /src for all git operations
- Build from /src
- Use github.sha environment variable for explicit checkout
Previous failure: git clone tried to clone into /workspace which already exists
Fix:
- Remove git clone step
- Forgejo automatically checks out repo into current directory
- Just install git, get commit info, build, and push
- Much simpler and cleaner
Previous run failed because:
- rust:1.83-bookworm container lacks Node.js (needed for actions/checkout)
- Docker not available in the rust container
- actions/checkout@v4 is a third-party action that needs Node
Solution:
- Use docker:27-dind container (has docker + git preinstalled)
- Replace actions/checkout with direct git clone + checkout
- All steps run directly in the docker container
This matches Forgejo's native environment better than trying to run
GitHub Actions inside a Rust container.
Gitea 1.27.0-rootless looks for workflows in .gitea/workflows/, not .forgejo/.
Removed unused .forgejo/ directory entirely.
Workflow is now at: .gitea/workflows/build.yaml
rock