Daniel Maksymilian Syrnicki e9e8bd3319 ci: run build-iso on the runner host (DooD path fix) ... 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>		2026-04-14 18:50:47 +02:00
..
build-iso.yml	ci: run build-iso on the runner host (DooD path fix)	2026-04-14 18:50:47 +02:00
ci.yml	ci: attach build-iso job to DinD network, pin lychee-action source	2026-04-14 18:37:54 +02:00