steve
574370e8d1
BREAKING: Remove Dockerfile.rocm, compose.rocm.yaml, and ROCm image build/push from the release pipeline. Remove AMD quick-start and ROCm references from README and DEVELOPER docs. Update docker-deployment and developer-docs specs to reflect CPU + NVIDIA only. The ROCm variant added significant complexity (4.2GB torch wheel, >20GB container) with limited usage. Users on AMD GPUs should stay on engine v3.2.x or switch to CPU mode. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.5 KiB
1.5 KiB
Why
AMD ROCm support adds significant complexity and maintenance burden to the project — the ROCm torch wheel alone is 4.2GB, the Dockerfile requires a multi-stage build with ROCm-specific runtime libraries, and the release pipeline must build/push additional images. The final container is >20Gb. ROCm support is less tested and less commonly used than CPU or NVIDIA. Removing it keeps the project focused and manageable.
What Changes
- BREAKING: Remove AMD ROCm Docker image (
Dockerfile.rocm) and compose file (compose.rocm.yaml) - BREAKING: Remove ROCm image build/push/release-notes from the engine release script
- Remove pre-built ROCm torch wheel from
assets/ - Remove all AMD/ROCm references from user-facing docs (README, DEVELOPER)
- Update docker-deployment spec to reflect CPU + NVIDIA only
Capabilities
New Capabilities
(none)
Modified Capabilities
docker-deployment: Remove AMD ROCm Docker image requirement and all ROCm-specific scenarios. Deployment now covers CPU and NVIDIA only.
Impact
- Docker images: ROCm image variant no longer published
- Users: Anyone running KB on AMD GPUs will need to stay on the last version with ROCm support (3.2.x) or switch to CPU mode
- Release pipeline:
release-engine.shsimplified — only CPU and NVIDIA images - Repository size: ~4.2GB reduction by removing the torch wheel from
assets/ - Docs: README and DEVELOPER updated to remove AMD quick-start and build instructions