Skip to content

containers: alma-8 for arm64, multi-arch images; arch in tarball names - #67

Merged
KonradBreitsprecherBkd merged 1 commit into
mainfrom
feature/el8-aarch64-image
Nov 17, 2026
Merged

KonradBreitsprecherBkd merged 1 commit into
mainfrom
feature/el8-aarch64-image

Conversation

@KonradBreitsprecherBkd

Copy link
Copy Markdown
Contributor

Prepares the el8 aarch64 tarball (feature/linux-tarballs-el8-aarch64). Its package run (43869387870) failed at Pull image for alma-8-aarch64-tgz, because alma-8:main exists only for x86_64.

Build Images (build-images.yml)

  • Each architecture is built natively on its own runner (ubuntu-latest / ubuntu-22.04-arm) and pushed as :sha-<short>-<arch>. provenance: false keeps these as plain image manifests.
  • A new manifest job combines the architectures of each image with docker buildx imagetools create into a multi-arch :sha-<short>, plus :main on the default branch. It writes the digest of the combined image to the job summary; that digest is the one to pin in release/packages.json.
  • alma-8 is built for amd64 and arm64. The other images keep their single architecture (ubuntu-2204 arm64, all others amd64).
  • The manifest job 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.
  • The smoke test prints uname -m.

release/packages.json can then use alma-8:main (or later its digest) on both runners.

Tarball name (scripts/silkit_tgz.py)

package_name() hardcoded x86_64. It now uses platform.machine() of the build container, so the arm64 build produces silkit-<ver>.el8.aarch64.tar.gz and 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-tgz entry in release/packages.json stays on feature/linux-tarballs-el8-aarch64 and needs a rebase after this is merged.

Tested

🤖 Generated with Claude Code

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>
@KonradBreitsprecherBkd

Copy link
Copy Markdown
Contributor Author

@snps-fiodorov

Your request showed a missing piece: building one distro for several architectures. Two things were x86_64 only:

  • Build image: alma-8 was only built on the x86_64 runner, so there was no arm64 image to pull. Build Images now builds each architecture natively and publishes :main as a multi-arch image, so the same image reference works on both runners.
  • Tarball name: silkit_tgz.py hardcoded x86_64. The name now uses the build machine's architecture, so your target produces silkit-.el8.aarch64.tar.gz.

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 snps-fiodorov left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

thanks a ton @KonradBreitsprecherBkd !

@KonradBreitsprecherBkd
KonradBreitsprecherBkd merged commit 04e0825 into main Nov 17, 2026
5 of 7 checks passed
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.

2 participants