Repository navigation
containers: alma-8 for arm64, multi-arch images; arch in tarball names - #67
Merged
Merged
Conversation
Every architecture is built natively on its own runner and pushed as :sha-<short>-<arch>. A manifest job combines them into a multi-arch :main / :sha-<short> per image, so release/packages.json can use the same image reference on x86_64 and arm64 runners. alma-8 is built for amd64 and arm64; the other images keep their single architecture. The tarball name takes the architecture from the build machine instead of hardcoding x86_64, so an el8 build on arm64 produces silkit-<version>.el8.aarch64.tar.gz. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
Your request showed a missing piece: building one distro for several architectures. Two things were x86_64 only:
Once this is merged and Build Images has run on main, rebase your branch onto main. Your packages.json entry can stay as it is. |
snps-fiodorov
approved these changes
Nov 16, 2026
snps-fiodorov
left a comment
Collaborator
There was a problem hiding this comment.
thanks a ton @KonradBreitsprecherBkd !
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares the el8 aarch64 tarball (
feature/linux-tarballs-el8-aarch64). Its package run (43869387870) failed at Pull image foralma-8-aarch64-tgz, becausealma-8:mainexists only for x86_64.Build Images (
build-images.yml)ubuntu-latest/ubuntu-22.04-arm) and pushed as:sha-<short>-<arch>.provenance: falsekeeps these as plain image manifests.manifestjob combines the architectures of each image withdocker buildx imagetools createinto a multi-arch:sha-<short>, plus:mainon the default branch. It writes the digest of the combined image to the job summary; that digest is the one to pin inrelease/packages.json.alma-8is built for amd64 and arm64. The other images keep their single architecture (ubuntu-2204arm64, all others amd64).manifestjob also runs when another image failed. Each image is combined from the:sha-<short>-<arch>tags of the same commit, so a failed build can't be mixed with an older one.uname -m.release/packages.jsoncan then usealma-8:main(or later its digest) on both runners.Tarball name (
scripts/silkit_tgz.py)package_name()hardcodedx86_64. It now usesplatform.machine()of the build container, so the arm64 build producessilkit-<ver>.el8.aarch64.tar.gzand the asset globs of the new target match. The x86_64 names stay the same. README updated.Not in this PR
The
alma-8-aarch64-tgzentry inrelease/packages.jsonstays onfeature/linux-tarballs-el8-aarch64and needs a rebase after this is merged.Tested
alma-8on the arm64 runner. On a PR themanifestjob is skipped, as no images are pushed; it first runs onmain.ubuntu-2004still needs containers: use the regular Ubuntu archive instead of snapshot.ubuntu.com #66 to get past the snapshot errors.🤖 Generated with Claude Code