fix: fix pytorch in the cuda11 image#4841
Conversation
As reported by deepmodeling#4837 (comment), the pytorch in the cuda 11 image is currently cuda12. Signed-off-by: Jinzhe Zeng <jinzhe.zeng@ustc.edu.cn>
for more information, see https://pre-commit.ci
📝 WalkthroughWalkthroughThis update removes unnecessary blank lines from multiple documentation files to improve formatting consistency and modifies the Dockerfile to change how the CUDA 11 PyTorch backend is specified during installation, switching from explicit PyTorch installation to setting an environment variable for backend selection. No functional or API changes are made. Changes
Possibly related PRs
Suggested reviewers
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (30)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
source/install/docker/Dockerfile (1)
11-13:torchgets requested twice – potential re-download/downgradeImmediately after the manual install, the extras string
[..,torch]triggers another resolution step without the custom index, which can:
- waste time (already-satisfied check), or
- accidentally pull/override with the CPU wheel if a newer patch appears.
A simple guard avoids the duplicate requirement:
- && uv pip install "$(ls /dist/deepmd_kit${VARIANT}-*manylinux*_x86_64.whl)[gpu,cu${CUDA_VERSION},lmp,ipi,torch]" \ + && EXTRAS="gpu,cu${CUDA_VERSION},lmp,ipi" \ + && [ "${CUDA_VERSION}" != 11 ] && EXTRAS="$EXTRAS,torch" \ + && uv pip install "$(ls /dist/deepmd_kit${VARIANT}-*manylinux*_x86_64.whl)[$EXTRAS]" \
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
doc/model/show-model-info.md(0 hunks)doc/train/multi-task-training.md(0 hunks)source/install/docker/Dockerfile(1 hunks)
💤 Files with no reviewable changes (2)
- doc/train/multi-task-training.md
- doc/model/show-model-info.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (29)
- GitHub Check: Build wheels for cp311-win_amd64
- GitHub Check: Build wheels for cp310-manylinux_aarch64
- GitHub Check: Build wheels for cp311-manylinux_x86_64
- GitHub Check: Build wheels for cp311-macosx_x86_64
- GitHub Check: Build wheels for cp311-macosx_arm64
- GitHub Check: Build wheels for cp311-manylinux_x86_64
- GitHub Check: Test Python (6, 3.12)
- GitHub Check: Test Python (5, 3.12)
- GitHub Check: Test Python (6, 3.9)
- GitHub Check: Test Python (1, 3.9)
- GitHub Check: Test Python (4, 3.9)
- GitHub Check: Test Python (4, 3.12)
- GitHub Check: Test Python (5, 3.9)
- GitHub Check: Test Python (3, 3.9)
- GitHub Check: Test Python (1, 3.12)
- GitHub Check: Test Python (3, 3.12)
- GitHub Check: Test Python (2, 3.9)
- GitHub Check: Test Python (2, 3.12)
- GitHub Check: Build C library (2.18, libdeepmd_c.tar.gz)
- GitHub Check: Build C library (2.14, >=2.5.0rc0,<2.15, libdeepmd_c_cu11.tar.gz)
- GitHub Check: Build C++ (clang, clang)
- GitHub Check: Build C++ (rocm, rocm)
- GitHub Check: Build C++ (cuda120, cuda)
- GitHub Check: Build C++ (cpu, cpu)
- GitHub Check: Build C++ (cuda, cuda)
- GitHub Check: Test C++ (false)
- GitHub Check: Test C++ (true)
- GitHub Check: Analyze (c-cpp)
- GitHub Check: Analyze (python)
Signed-off-by: Jinzhe Zeng <jinzhe.zeng@ustc.edu.cn>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## devel #4841 +/- ##
=======================================
Coverage 84.72% 84.72%
=======================================
Files 699 699
Lines 68181 68182 +1
Branches 3541 3541
=======================================
+ Hits 57769 57770 +1
- Misses 9279 9280 +1
+ Partials 1133 1132 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
As reported by deepmodeling#4837 (comment), the pytorch in the cuda 11 image is currently cuda12. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Cleaned up documentation formatting by removing unnecessary blank lines for improved readability and consistency. * **Refactor** * Improved Docker installation process to better manage PyTorch backend selection for CUDA 11 environments. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: Jinzhe Zeng <jinzhe.zeng@ustc.edu.cn> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
As reported by #4837 (comment), the pytorch in the cuda 11 image is currently cuda12.
Summary by CodeRabbit
Chores
Refactor