Harden CPU AI image builds
This commit is contained in:
@@ -43,6 +43,18 @@ AI dependencies remain separate in the `ai` optional dependency group and must
|
||||
not be installed by the default Docker backend image unless an explicit AI image
|
||||
or profile is introduced later.
|
||||
|
||||
The opt-in Unraid all-in-one AI build is CPU-oriented because its documented
|
||||
runtime sets `YOLO_DEVICE=cpu`. It installs the pinned PyTorch/torchvision pair
|
||||
from PyTorch's CPU wheel index before installing the `ai` extra. This avoids
|
||||
shipping unused CUDA runtime libraries. The index and versions remain explicit
|
||||
Docker build arguments so a future, separately validated GPU image can override
|
||||
them without changing the base dependency group.
|
||||
|
||||
Docker dependency metadata is copied before application source. Backend source
|
||||
changes therefore reuse the dependency layer while changes to `pyproject.toml`
|
||||
still invalidate it correctly. Runtime GIS and YOLO import/preflight smokes run
|
||||
after the complete backend source is copied.
|
||||
|
||||
## Approved AI
|
||||
|
||||
- PyTorch
|
||||
|
||||
Reference in New Issue
Block a user