fix(ci): build the CUDA 13 image on Ubuntu 24.04 - #11143
Merged
Merged
Conversation
The amd64 `-gpu-nvidia-cuda-13` image is the only runtime image still built FROM ubuntu:22.04. The Ubuntu 24.04 migration (#7769) bumped its `ubuntu-version` to 2404 but left `base-image` on jammy, so the image ships glibc 2.35 while adding the noble CUDA apt repository, and every backend it unpacks is built on noble. Backends therefore cannot dlopen the libraries they bundle. The vLLM backend dies at import time with: OSError: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /backends/cuda13-vllm/lib/libnuma.so.1) and torchcodec finds no usable libavutil because jammy ships ffmpeg 4.x (libavutil.so.56) while torchcodec looks for .so.57 through .so.60. Add a spec over the build matrices that fails when a base image and the `ubuntu-version`/`ubuntu-codename` it is paired with disagree, or when the runtime images are split across Ubuntu releases. Entries whose base image does not name a release (JetPack) are left alone. The `base-grpc-cuda-13-amd64` builder base stays on jammy: it only compiles backends, and a lower glibc floor in a builder is safe. Fixes #11059 Assisted-by: Claude:claude-opus-5 golangci-lint Signed-off-by: Ettore Di Giacinto <mudler@localai.io>
mudler
reviewed
Jul 27, 2026
| @@ -0,0 +1,13 @@ | |||
| package buildmatrix_test | |||
Collaborator
Author
There was a problem hiding this comment.
Removed in 206ab8d — the whole pkg/buildmatrix package is gone, so the PR is now just the two ubuntu:22.04 -> ubuntu:24.04 lines. Squash-merging leaves master with only that diff.
Per review, the CI matrix guard does not belong in the tree. Only the base image bump remains. Assisted-by: Claude:claude-opus-5 [Claude Code] Signed-off-by: Ettore Di Giacinto <mudler@localai.io>
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
2 participants
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.
What
The amd64
-gpu-nvidia-cuda-13image is the only runtime image still builtFROM ubuntu:22.04. This moves it toubuntu:24.04, matching every other image and every backend.Fixes #11059
Why
The Ubuntu 24.04 migration (#7769) bumped that matrix entry's
ubuntu-versionto2404and addedubuntu-codename: noble, but thebase-imageline fell outside the diff hunk and stayed on jammy. The result is an image running glibc 2.35 that installs CUDA 13 from the noble apt repository, and that then unpacks backends built on noble (vllmcuda13 usesbase-image: "ubuntu:24.04",.github/backend-matrix.yml:1204).Backends consequently cannot
dlopenthe libraries they bundle. From the report:The torchcodec failures higher in that log are the same root cause seen from the other side: jammy ships ffmpeg 4.x (
libavutil.so.56) while torchcodec probes.so.57through.so.60. Noble's ffmpeg 6.1 provides.so.58, solibtorchcodec_core6.soloads.Changes
Two lines,
ubuntu:22.04->ubuntu:24.04for the cuda-13 amd64 entry in.github/workflows/image.ymland.github/workflows/image-pr.yml.Not changed
base-grpc-cuda-13-amd64inbase-images.ymlstays on jammy. It is a builder base only: the backends it compiles haveubuntu:24.04final stages, and a lower glibc floor in a builder is forward-compatible. Moving it would force cold rebuilds of the cuda-13llama-cpp(5h+) andturboquant(6h) backends for no user-visible gain.Testing
CI built the cuda-13 amd64 image on
ubuntu:24.04successfully on this branch (image-build (cublas, 13, 0, linux/amd64, ..., ubuntu:24.04, ...)), which is the end-to-end check that matters here.