fix: container CI pipeline — DinD checkout, SSH, and Dockerfile fixes #26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development_fix_container_ci"
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?
Summary
Fix the container build CI pipeline (build-container.yaml) to work e2e in Forgejo Actions with Docker-in-Docker.
Changes
build-container.yaml:
actions/checkout@v4with manualgit clone(alpine musl/glibc incompatibility)nodejstoapk add(Docker actions are JS-based and need Node)env:block to preserve multiline key~/.ssh/configwithStrictHostKeyChecking accept-newinstead ofssh-keyscanDockerfile:
zinit_sdkpath dependency before cargo buildhero_services_server, nothero_zero)hero_zero install-serviceloop (binary doesn't exist yet)Confirmed Working
Run 352 — all steps pass, image pushed to registry:
forge.ourworld.tf/lhumina_code/hero_zero:devforge.ourworld.tf/lhumina_code/hero_zero:latestCloses #25
Direct ${{ secrets }} interpolation in run blocks mangles multi-line SSH keys. Pass via env: block instead, matching the pattern used in build.yaml which works. Co-Authored-By: mik-tf <mik@threefold.io>docker/setup-buildx-action, docker/login-action, and docker/build-push-action are JavaScript actions that need Node.js in the runner. Without it, they fail with exit 127 ("node: not found"). Co-Authored-By: mik-tf <mik@threefold.io>WIP: fix: make container build CI pipeline work e2eto fix: container CI pipeline — DinD checkout, SSH, and Dockerfile fixesSuperseded by #43 (combined deploy branch with all PRs merged).
Pull request closed