ci: drop ineffective container.options override for build-iso

forgejo-runner 6.4 filters `--network` out of `container.options`, so
the workflow-level override was silently ignored and the job kept
landing on a per-task network where `docker-in-docker` didn't resolve.
Fixed at the right level by editing the runner's `/data/config.yml`
(`container.network: "forgejo-runner_default"`) and restarting the
forgejo-runner container — every job now joins the shared network so
DOCKER_HOST=tcp://docker-in-docker:2375 just works.

Workflow trimmed back to only what's needed: DOCKER_HOST env pin. The
default runner image (catthehacker/ubuntu:act-latest) already has the
docker CLI.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

.forgejo/workflows/build-iso.yml

@@ -16,14 +16,12 @@ jobs:
   build-iso:
     runs-on: ubuntu-latest
     timeout-minutes: 30
-    # Attach the job container to `forgejo-runner_default` so the
+    # DOCKER_HOST points the docker CLI at the DinD sidecar. The sidecar's
-    # `docker-in-docker` hostname (the DinD sidecar) is DNS-resolvable.
+    # hostname is DNS-resolvable because forgejo-runner is configured with
-    # Without this the job runs on its own per-job network and DOCKER_HOST
+    # `container.network: "forgejo-runner_default"`, which attaches every
-    # resolves nowhere. catthehacker/ubuntu:act-latest already ships
+    # job container to the shared network where docker-in-docker lives.
-    # docker CLI, so we don't need to apt-install anything.
+    # The default `ubuntu-latest` image (catthehacker/ubuntu:act-latest)
-    container:
+    # already ships the docker CLI.
-      image: catthehacker/ubuntu:act-latest
-      options: --network forgejo-runner_default
     env:
       DOCKER_HOST: tcp://docker-in-docker:2375
     steps: