Skip to content

fix(docker): default TT_SMI_COMMIT_SHA_OR_TAG to an existing tag (v6.8.1) - #5569

Open
pasta-paul wants to merge 1 commit into
tenstorrent:mainfrom
pasta-paul:fix/tt-smi-tag-v6
Open

pasta-paul wants to merge 1 commit into
tenstorrent:mainfrom
pasta-paul:fix/tt-smi-tag-v6

Conversation

@pasta-paul

Copy link
Copy Markdown

Problem

vllm-tt-metal/vllm.tt-metal.src.dev.Dockerfile defaults:

ARG TT_SMI_COMMIT_SHA_OR_TAG=v3.1.1

but tenstorrent/tt-smi no longer has a v3.1.1 tag — its tags are v6.x (git ls-remote --tags
shows v6.0.0 … v6.8.1; no v3.*). The build step:

RUN git clone https://github.com/tenstorrent/tt-smi.git ${TT_SMI_DIR} \
 && cd ${TT_SMI_DIR} && git checkout ${TT_SMI_COMMIT_SHA_OR_TAG} ...

therefore fails with exit code 128 (pathspec 'v3.1.1' did not match), and the whole image build
stops at that layer.

Reproduced 2026-11-12 building tt-metal 35a89ef25c01d54e12d00494468eff1a1110f951 +
vllm-tt-plugin d84049edcece77c64772a39e92f920f5679efce4 (vLLM 0.30.0) via
scripts/build_single_docker.sh on a QuietBox 2. Changing the default to v6.8.1 (latest at
the time) makes the build complete.

Change

-ARG TT_SMI_COMMIT_SHA_OR_TAG=v3.1.1
+ARG TT_SMI_COMMIT_SHA_OR_TAG=v6.8.1

Verification

  • git ls-remote --tags https://github.com/tenstorrent/tt-smi.git | tail → latest v6.8.1.
  • With this change the tt-metal + vLLM image builds and the resulting server serves Qwen3.8-27B at
    max_num_seqs=4 with batched vision (127 ms TTFT, 38.8 tok/s single, 131 tok/s aggregate on a
    QuietBox 2).

Disclaimer: found and validated by Digby AI, an autonomous coding agent operating the
CQL.ca lab's QuietBox 2; the failure and the fix were reproduced on that hardware. Reviewed
and approved by Paul (@pasta-paul).

@pasta-paul
pasta-paul requested review from a team and bgoelTT as code owners November 12, 2026 22:54
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.

1 participant