The CI was failing because the rust:latest container doesn't have
Node.js, but the actions/checkout@v4 action requires Node.js to run.
Error: 'exec: node: executable file not found in /home/asoliver/.local/bin/:/home/asoliver/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/home/asoliver/.local/share/flatpak/exports/bin:/var/lib/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/usr/lib/rustup/bin'
Solution:
- Install Node.js before running checkout action
- For rust:latest containers: use NodeSource repository
- For docker:latest containers: use apk package manager
This allows the GitHub Actions checkout action to work in Forgejo.
The CI was stuck because 'runs-on: ubuntu-latest' doesn't match
any configured Forgejo runner labels.
Forgejo uses 'docker' as the default label for runners that support
containerized jobs. This matches the original workflow configuration
and should be picked up by your Forgejo runner.
The previous workflow was getting stuck because it was trying to pull
actions from GitHub (https://github.com/actions/cache@v3) which can
cause connectivity and compatibility issues in Forgejo.
Changes:
- Remove all external GitHub action dependencies except checkout
- Use Forgejo's built-in checkout@v4 action
- Remove caching steps (can be added later with Forgejo-native actions)
- Add explicit dependency installation step
- Use 'cargo build --release' for better optimization
This should make the CI more reliable and faster to start.
The original workflow was using GitHub-specific actions that don't exist
in Forgejo, causing CI to fail immediately with:
'repository not found: Not Found' for actions-rs/toolchain@v1
Key changes:
- Replace 'runs-on: docker' with 'runs-on: ubuntu-latest' and proper containers
- Remove 'actions-rs/toolchain@v1' (doesn't exist in Forgejo)
- Use 'rust:latest' container image instead which includes rustfmt, clippy, and cargo
- Update all action references to use full URLs (https://github.com/...)
- Use 'docker:dind' service for Docker-in-Docker support
- Remove 'docker/setup-buildx-action@v3' (not needed for basic docker build)
This workflow is now compatible with Forgejo and should run successfully.
Updated all jobs in the lint-and-build workflow to use the
Docker-labeled runner instead of ubuntu-latest.
Changes:
- lint job: runs-on: docker
- build job: runs-on: docker
- docker-build job: runs-on: docker
Benefits:
- Native Docker support
- Faster builds
- Better performance on local infrastructure
- Consistent with server setup
