ci: route the Eco image build through the runner egress proxy #142
Labels
No labels
burndown-2026-06
headless
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
c#
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-gaming/eco-app#142
Loading…
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?
Context
The container-native mod packaging path fails before publishing because
dotnet restorecannot reliably fetch the public NuGet v3 service index from the Forgejo runner DinD network. infrastructure#563 now owns an allowlisted in-cluster egress proxy and exposes its address to runner jobs asFORGEJO_EGRESS_PROXY.Work
Opt the application image build into the shared proxy through Docker predefined proxy build arguments. Keep the proxy value out of the Dockerfile and final image. Route the frontend, mod, and Python dependency hosts needed by this multi-stage build through the infrastructure allowlist.
Acceptance
HTTP_PROXYandHTTPS_PROXYfromFORGEJO_EGRESS_PROXY.Related: #111, #141, coilyco-flight-deck/infrastructure#563.