Repository navigation
build(docker): add ARM64 and DGX Spark container builds - #263
Merged
NandhaKishorM merged 3 commits intoSep 23, 2026
Merged
Conversation
The quickstart image builds natively on ARM64, and a DGX Spark override selects ARM64 with CUDA 13.0. PyTorch and the Python base image become build arguments, with torch pinned at 2.14.0, so a new torch release cannot change the image under an unrelated PR. PyTorch's ARM64 CUDA 13.0 wheels depend on cuSPARSELt 0.8.0 (torch 2.11) or 0.8.1 (torch 2.14), whose wheels declare an SBSA tag that pip check rejects. docker/check_torch.py checks the library is ELF64 AArch64 and loads it before correcting only that tag and its RECORD hash. Any other version that carries the same tag fails the build. CI runs the smoke job on native AMD64 and ARM64 runners and builds the Spark image without a GPU to check its CUDA libraries load. Co-authored-by: TheIrritainer <theirritainer@gmail.com>
NandhaKishorM#234 added laya-serve as its own service, so the Spark override repeats the ARM64, CUDA 13.0 and GPU settings for it, and its build takes the pinned torch version. The workflow validates the HTTP plus Spark combination, and the Spark additions sit apart from the other jobs so later workflow changes merge cleanly. Co-authored-by: TheIrritainer <theirritainer@gmail.com>
Owner
|
Thank you, native ARM64 builds and a DGX Spark compose file are a great fit for running Laya locally on more hardware, and working around the aarch64 cuSPARSELt wheel tag while keeping |
This was referenced Sep 23, 2026
baninaveen
pushed a commit
to baninaveen/laya
that referenced
this pull request
Sep 24, 2026
…M#263) * build(docker): add ARM64 and DGX Spark container builds The quickstart image builds natively on ARM64, and a DGX Spark override selects ARM64 with CUDA 13.0. PyTorch and the Python base image become build arguments, with torch pinned at 2.14.0, so a new torch release cannot change the image under an unrelated PR. PyTorch's ARM64 CUDA 13.0 wheels depend on cuSPARSELt 0.8.0 (torch 2.11) or 0.8.1 (torch 2.14), whose wheels declare an SBSA tag that pip check rejects. docker/check_torch.py checks the library is ELF64 AArch64 and loads it before correcting only that tag and its RECORD hash. Any other version that carries the same tag fails the build. CI runs the smoke job on native AMD64 and ARM64 runners and builds the Spark image without a GPU to check its CUDA libraries load. Co-authored-by: TheIrritainer <theirritainer@gmail.com> * docs(docker): credit the cuSPARSELt finding by handle * build(docker): run laya-serve on DGX Spark NandhaKishorM#234 added laya-serve as its own service, so the Spark override repeats the ARM64, CUDA 13.0 and GPU settings for it, and its build takes the pinned torch version. The workflow validates the HTTP plus Spark combination, and the Spark additions sit apart from the other jobs so later workflow changes merge cleanly. Co-authored-by: TheIrritainer <theirritainer@gmail.com> --------- Co-authored-by: TheIrritainer <theirritainer@gmail.com>
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.
This is the ARM64 and DGX Spark follow-up I mentioned on #45. It adds native Linux ARM64 builds of the quickstart image, keeps CPU as the default on both architectures, and adds
compose.spark.yamlto select ARM64 with CUDA 13.0 for a Spark.PyTorch's ARM64 CUDA 13.0 wheels depend on cuSPARSELt 0.8.0 (torch 2.11) or 0.8.1 (torch 2.14), and NVIDIA's aarch64 wheels for both declare
manylinux2014_sbsainside theirWHEELfile, sopip checkfails. 0.9.0 fixes the tag but no torch release pins it yet.docker/check_torch.pychecks the library is ELF64 AArch64 and loads it, then corrects only that tag and itsRECORDhash. If another version shows up with the same problem, the build fails instead of patching it. @TheIrritainer found this first in FastLaya.Other changes:
TORCH_VERSION(pinned at 2.14.0, the current release) andPYTHON_IMAGEare build args. Torch wasn't pinned, so a new release could've changed the image under an unrelated PR. The same check fails the build if the installed wheel doesn't match the requested index (cpu,cu128,cu130).ubuntu-latestandubuntu-24.04-arm, and aspark-buildjob builds the cu130 image on ARM64 and checks the CUDA libraries load. There's no GPU in CI, so that stops at installation.docs/docker-platforms.mdhas the platform notes and a command for anyone with a Spark to report real GPU results. It also says why Apple Silicon gets CPU in the container: Docker on a Mac runs Linux, so there's no MPS.Validation:
tests/test_docker_torch.pycovers the repair for both versions and makes sure anything else is left alone. It runs inside the image in CI.docker compose configpasses for every combination the workflow checks, including the Spark override.pip checkis clean, and the quickstart's SDK request runs online and again offline.laya-serveanswers/health, returns 401 without a token or with the wrong one, and 200 with all three answers for the sample request.2.14.0+cu130imports, cuSPARSELt loads (801), andpip checkis clean. No GPU on that machine, so this is the same installation check as the CI job.Spark GPU inference isn't tested yet. It needs someone with the hardware, and the docs say so.
Since #234 made
laya-serveits own service,compose.spark.yamlrepeats the Spark settings for it the same waycompose.cuda.yamldoes, and it builds with the pinned torch too.