ci(forgejo): let the amd64 runner reach the in-cluster registry and use docker #15
Loading…
Reference in a new issue
No description provided.
Delete branch "wt/forgejo-insecure-registry"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
Forgejo's container registry now lives in the cluster, reachable in-cluster only as the plain-HTTP ClusterIP
forgejo.forgejo.svc.cluster.local:3000. Docker treats only127.0.0.0/8as insecure, and the amd64 job container ships no docker CLI at all. Both breaksirius/osint-dashboard's build workflow (merged as #63), which was red from 2026-11-14 for exactly these reasons.Change (2 files)
apps/base/forgejo/runner-amd64.yaml— one dockerd flag:apps/base/forgejo/runner-configmap.yaml—amd64.tomlgets the same CLI injectionarm64.tomlalready has. Without it the job dies withdocker: command not foundon its firstdocker login:docker_hostis dropped, not kept alongsideoptions— having both mounts the socket twice ("Duplicate mount point"). No--memorycap, unlike arm64: this runner also carries the existing amd64 release builds, which were already uncapped.Only the amd64 runner is touched:
amd64is the label the osint build uses (the cluster is amd64, and its images must match), and the arm64/deploy runners never build them.Rebased onto #14
The first revision conflicted with #14 (stale dind pid), which landed in master after this branch opened. Rebased; the resolved
dockerdblock keeps #14'srm -f /var/run/docker.pid /var/run/docker.sockand adds the registry flag.mergeable: trueas ofa385a8a.Evidence — the pipeline actually works
Both files were applied to the live cluster with Flux suspended (
appskustomization), the osint workflow was dispatched on its branch, and the runner was then handed back to Flux (which reverted the cluster to master — verified:amdb64.tomlback todocker_host, dockerd back to no flag).Run 1365, job 2008,
runs_on: [amd64]→ success:Registry confirms the artifact (created 2026-11-17T20:11:14Z):
Manifests rendered + shell-checked after the rebase:
This must merge for CI to stay green. Flux has reverted the live runner to master, so until it lands the osint build fails at
docker loginagain (HTTPS against the plain-HTTP ClusterIP).1473f45fc6toa385a8a360ci(forgejo): let the amd64 dind daemon push to the in-cluster registryto ci(forgejo): let the amd64 runner reach the in-cluster registry and use dockerPost-merge verification (no manual apply)
Flux reconciled
appsto master@3965478 and rolled the dind container. Live state:Then the osint workflow was dispatched on
master(run 1367, job 2010,runs_on: [amd64]) → success, all three images built and pushed:Registry (package list, container type):