OLS-3235 Make lightspeed-rag-content a multi-arch image#769
Open
onmete wants to merge 2 commits into
Open
Conversation
Add arm64 build leg to the own-app-lightspeed-rag-content pipelines to produce a proper OCI manifest list with both amd64 and arm64 variants. This unblocks Konflux multi-arch builds of lightspeed-service which consumes this image. Changes: - Containerfile: add REQUIREMENTS_FILE build arg to support architecture-specific Python dependencies - requirements.arm64.txt: arm64-compatible requirements with aarch64 torch wheel from Red Hat package registry - Pipeline YAMLs: add build-container-arm64 task using FLAVOR=cpu on linux/arm64, enable build-image-index to produce manifest list, prefetch both GPU and arm64 requirements The arm64 variant uses CPU-only PyTorch on ubi9/python-312 (multi-arch) as the builder and produces identical vector DB data. The final image is ubi-minimal with architecture-independent content. Co-authored-by: Cursor <cursoragent@cursor.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Contributor
Author
|
/retest |
The Red Hat torch CPU wheel requires libmpi_cxx.so.40 at runtime (used for distributed tensor operations). On the GPU base image this is pre-installed, but ubi9/python-312 (cpu-base) doesn't have it. Fix by copying the OpenMPI shared libraries from the gpu-base stage (which is already pulled during the build) into the builder stage and updating the dynamic linker cache. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
/hold |
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.
Summary
own-app-lightspeed-rag-contentKonflux pipelines to produce a multi-arch OCI manifest list (amd64 + arm64)lightspeed-servicemulti-arch builds which consume this image and were failing with:Base image ... has architecture 'amd64', expected 'arm64'ubi9/python-312and produces identical vector DB contentChanges
ContainerfileREQUIREMENTS_FILEbuild arg for arch-specific depsrequirements.arm64.txt.tekton/own-app-*-push.yamlbuild-container-arm64task, enable image index.tekton/own-app-*-pull-request.yamlDesign
FLAVOR=cpuwithubi9/python-312(multi-arch) as the builder basebuild-image-indexaggregates both arch images into a manifest listubi-minimalbase image digest is already a manifest list with arm64 support (verified)requirements.arm64.txtis identical torequirements.cpu.txtexcept torch points to thelinux_aarch64.whl(hash verified by download)Test plan
lightspeed-servicearm64 build can consume the new multi-arch image referenceReferences
Made with Cursor