rock/homelab-frontend
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(ci): mount /docker-certs/client into the build job container
Build / Build and push image (push) Failing after 13s
Details
CI / Test, vet, build (push) Successful in 1m49s
Details

Browse Source
This commit is contained in:
Story Crater Bot
2026-08-21 15:55:23 -07:00
parent 0e6ebe7353
commit 7b265b8338
1 changed files with 11 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/build.yaml
+11 -3
View File
@@ -18,10 +18,18 @@ jobs:
runs-on: docker runs-on: docker
container: container:
image: docker:27-cli image: docker:27-cli
# The runner's dind sidecar shares the pod network and the mTLS cert # The runner's dind sidecar shares the pod network, so the daemon is
# emptyDir, so the daemon is reachable on localhost with the client certs # reachable on localhost -- that part needs no extra config. The mTLS
# dind generated at startup. # certs dind generates at startup do NOT come along for free, though:
# they live in an emptyDir mounted into the runner/dind containers, not
# into containers a workflow spins up. Job containers get no bind mounts
# at all unless the path is in the runner's container.valid_volumes
# allowlist (empty by default -- confirmed live, this exact mount was
# rejected until the runner's Helm chart added a config.yaml scoping
# valid_volumes to exactly this path).
options: --network host options: --network host
volumes:
- /docker-certs/client:/docker-certs/client:ro
env: env:
DOCKER_HOST: tcp://localhost:2376 DOCKER_HOST: tcp://localhost:2376
DOCKER_TLS_VERIFY: "1" DOCKER_TLS_VERIFY: "1"