| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2026-05-29 | 1.4 kB | |
| v0.17.5 source code.tar.gz | 2026-05-29 | 5.7 MB | |
| v0.17.5 source code.zip | 2026-05-29 | 6.5 MB | |
| Totals: 3 Items | 12.3 MB | 0 | |
What's changed
Bug fix: GPU Docker images now install the CUDA build of PyTorch
The GPU Docker images (ludwig-gpu, ludwig-ray-gpu) were incorrectly shipping the CPU build of PyTorch (torch==2.12.0 without a +cu* suffix) despite being GPU images. This meant GPU training silently fell back to CPU.
Root cause (two issues):
-
The
--force-reinstallstep used--extra-index-urlinstead of--index-url. With--extra-index-url, pip checks PyPI first and finds the CPU wheel (torch==2.12.0) there, so it never looks at the PyTorch CUDA index. -
The CUDA index suffix was
cu124, buttorch==2.12.0is not published on the cu124 index (which only goes up to2.6.0+cu124). The fix switches tocu126, wheretorch==2.12.0+cu126is available.
Fix:
- Changed
--extra-index-url→--index-urlon the force-reinstall step in both GPU Dockerfiles so pip goes exclusively to the PyTorch wheel server. - Changed
cu124→cu126throughout both GPU Dockerfiles (including the Ray base image tag).
Verified locally: torch==2.12.0+cu126 with CUDA build version: 12.6 confirmed inside the rebuilt image.
Updated Docker images (0.17.5)
ludwigai/ludwig:0.17.5— CPUludwigai/ludwig-gpu:0.17.5— CUDA 12.6 (torch 2.12.0+cu126)ludwigai/ludwig-ray:0.17.5— CPU + Rayludwigai/ludwig-ray-gpu:0.17.5— CUDA 12.6 + Ray (torch 2.12.0+cu126)