fix: make build-container.yaml CI pipeline work e2e #25
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_services_archive#25
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Problem
The
build-container.yamlworkflow (DinD container build + push to registry) fails at the Checkout step. Only run was on Feb 11 (run 247) — failed immediately.The
build.yamlworkflow (test/check/build) works fine because it usesghcr.io/despiegk/builder:latest(full ubuntu). The container build usesdocker:24-dind(alpine), whereactions/checkout@v4likely fails due to glibc/musl mismatch.Fix
Replace
actions/checkout@v4with manualgit cloneusing FORGEJO_TOKEN. This avoids the node/glibc dependency entirely and is the standard approach for alpine-based DinD containers.Also fix the same issue in the
create-releasejob.Validation
Trigger via
workflow_dispatchand confirm the full pipeline completes:forge.ourworld.tf/lhumina_code/hero_zeroRelated