Skip to content

fix: correct scc Linux arch mapping in Dockerfile.agent#13

Closed
t-rhex wants to merge 1 commit into
mainfrom
fix/scc-linux-arch
Closed

fix: correct scc Linux arch mapping in Dockerfile.agent#13
t-rhex wants to merge 1 commit into
mainfrom
fix/scc-linux-arch

Conversation

@t-rhex
Copy link
Copy Markdown
Owner

@t-rhex t-rhex commented Mar 22, 2026

Summary\n- map non-arm64 Linux builds to for release asset lookup\n- keep arm64 mapping unchanged\n\n## Why\nCI Docker agent image build fails with 404 on because upstream release assets use .\n\n## Validation\n- Ran locally\n- Build now passes through the previous failing install step and completes successfully

Fix Docker agent image build by mapping non-arm64 Linux to x86_64 for scc release assets.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
@t-rhex
Copy link
Copy Markdown
Owner Author

t-rhex commented Mar 22, 2026

LGTM. One-line Dockerfile fix, docker-build CI passes. lint/typecheck failures are pre-existing on main. Ready to merge.

—Dex

Copy link
Copy Markdown
Owner Author

@t-rhex t-rhex left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CTO Review: APPROVED

One-liner that fixes the Docker build 404 from the CI escalation (VOYA-17). The scc release uses x86_64 not amd64 for the tarball filename. Good catch.

—Kai

@t-rhex
Copy link
Copy Markdown
Owner Author

t-rhex commented Mar 22, 2026

Closing: scc Linux arch fix has been merged into PR #11 (devops/node24-actions-runtime), which now has all CI jobs green.

@t-rhex t-rhex closed this Mar 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant