Daniel Maksymilian Syrnicki
e9e8bd3319
Now that the runner uses docker-outside-of-docker, volume mounts in `build.sh` (`docker run -v \$REPO_ROOT:/work ...`) are interpreted by host docker — so `\$REPO_ROOT` must be a real host path. When the job runs inside a job container, `\$REPO_ROOT` is only valid in the job container's filesystem namespace and host docker can't find it, hence `bash: /work/iso/build.sh: No such file or directory`. Fix: switch `runs-on` to `self-hosted`. Forgejo-runner exposes that label out of the box and, with no matching container image mapping, runs steps directly on the runner VM. Checkout writes to a real host path; `docker run -v …` then mounts a path both the outer CLI and host docker agree on. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
42 lines
1.2 KiB
YAML
42 lines
1.2 KiB
YAML
name: Build ISO
|
|
|
|
# Full ISO build is ~15-20 min. Only run on push-to-main and manual
|
|
# dispatch so feature-branch iteration stays fast. See
|
|
# memory/project_ci_branching for the rationale.
|
|
on:
|
|
push:
|
|
branches: [main]
|
|
workflow_dispatch:
|
|
|
|
concurrency:
|
|
group: build-iso-${{ github.ref }}
|
|
cancel-in-progress: true
|
|
|
|
jobs:
|
|
build-iso:
|
|
# Run directly on the runner host, not inside a job container.
|
|
# `build.sh` does `docker run -v $REPO_ROOT:/work archlinux:latest`,
|
|
# and host docker interprets the volume source as a host path — so
|
|
# $REPO_ROOT has to be a path on the host, which it only is when
|
|
# we skip the job-container wrapping. The runner VM has git + docker.
|
|
runs-on: self-hosted
|
|
timeout-minutes: 30
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
|
|
- name: Build ISO
|
|
run: ./iso/build.sh
|
|
|
|
- name: Report ISO hash
|
|
run: |
|
|
iso=$(ls iso/out/*.iso | head -1)
|
|
echo "ISO: $iso"
|
|
sha256sum "$iso"
|
|
|
|
- name: Upload ISO artifact
|
|
uses: actions/upload-artifact@v4
|
|
with:
|
|
name: furtka-iso
|
|
path: iso/out/*.iso
|
|
retention-days: 14
|
|
if-no-files-found: error
|