You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the only way to know which GPU driver a fleet instance runs is to
provision it and run a task there.
Now shim detects the host GPU driver version on start (`nvidia-smi` for NVIDIA,
`amd-smi` for AMD, `/sys/module/tenstorrent/version` for Tenstorrent) and reports
it via the new `GET /api/instance/info` endpoint. The server stores it in
`JobProvisioningData`, so that no migration is needed, and exposes it as
`Instance.gpu_driver` and as a DRIVER column in `dstack fleet -v`.
Notes:
- Instance info reports facts observed by shim, as opposed to `/api/components`,
which reports software managed by shim.
- GPU hosts are asked on every instance check, as the facts change when shim
restarts, e.g., after a driver upgrade, which the server does not necessarily
observe. The provisioning data is only updated if the driver changed.
- SSH fleets are also asked at deploy time, so that the driver is known as soon
as the instance is ready.
- The driver stays unknown on hosts without GPUs, if detection fails, and on
backends where shim does not run (runpod, vastai, kubernetes).
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
0 commit comments