Skip to content

Add Nvidia Spark GB10 Docker image#1464

Closed
ich777 wants to merge 0 commit into
leejet:masterfrom
ich777:master
Closed

Add Nvidia Spark GB10 Docker image#1464
ich777 wants to merge 0 commit into
leejet:masterfrom
ich777:master

Conversation

@ich777
Copy link
Copy Markdown
Contributor

@ich777 ich777 commented Apr 28, 2026

  • Add Dockerfile Dockerfile.cuda-spark with optimized build flags
  • Modify build/publish matrix to support arm64 build for Nvidia Spark GB10

@ich777
Copy link
Copy Markdown
Contributor Author

ich777 commented May 12, 2026

@leejet is that something that can be implemented?
It would be super cool to also have an image for the Nvidia Spark GB10

@leejet
Copy link
Copy Markdown
Owner

leejet commented May 17, 2026

I think the idea makes sense, but I don’t think this needs a separate Dockerfile.cuda-spark in its current form. From the diff, the Spark variant is still using the same CUDA backend and build flow as the existing CUDA image; the main differences appear to be build parameters:

  • platform=linux/arm64
  • CUDA_VERSION=13.0.0
  • UBUNTU_VERSION=24.04
  • CMAKE_CUDA_ARCHITECTURES=121
  • GGML_CUDA_FA_ALL_QUANTS=ON

So this looks more like a CUDA build variant for DGX Spark / GB10 rather than a distinct Dockerfile target that needs to be maintained separately.

I would suggest parameterizing the existing Dockerfile.cuda instead of duplicating most of it into Dockerfile.cuda-spark. For example, Dockerfile.cuda could expose build args such as:

ARG CUDA_VERSION=...
ARG UBUNTU_VERSION=...
ARG CUDA_ARCHITECTURES=...
ARG GGML_CUDA_FA_ALL_QUANTS=...

@ich777
Copy link
Copy Markdown
Contributor Author

ich777 commented May 17, 2026

So this looks more like a CUDA build variant for DGX Spark / GB10 rather than a distinct Dockerfile target that needs to be maintained separately.

Oh okay, I can change that.
My initial thought for a dedicated file was that the Spark uses a somewhat unique combination (SM 121 + CUDA 13.0, where other targets use either SM 120 or SM 121 with CUDA 13.1+) but you are probably right, I'll change the PR if that would the repo more nicely.

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