Skip to content

Remove orphaned nvidia-*-cu11 pins after torch 2.13.0 upgrade - #189

Merged
William Blum (blumu) merged 1 commit into
mainfrom
wiblum/remove-orphaned-cu11
Aug 25, 2026
Merged

William Blum (blumu) merged 1 commit into
mainfrom
wiblum/remove-orphaned-cu11

Conversation

@blumu

Copy link
Copy Markdown
Contributor

Summary

Follow-up cleanup after the torch 2.13.0 upgrade (#186). Removes four explicitly-pinned CUDA 11 packages that are no longer needed by any dependency.

Why

torch==2.13.0 uses the CUDA 13 (cu13) wheel stack (nvidia-cublas, nvidia-cudnn-cu13, etc.). The following cu11 pins in requirements.dev.txt were left over from a much older torch and are now dead weight — pip/uv installs them as explicit top-level requirements even though nothing depends on them:

  • nvidia-cublas-cu11==11.10.3.66
  • nvidia-cuda-nvrtc-cu11==11.7.99
  • nvidia-cuda-runtime-cu11==11.7.99
  • nvidia-cudnn-cu11==8.5.0.96

Removing them avoids installing ~1.5 GB of unused CUDA 11 libraries alongside the current CUDA 13 stack.

Verification

  • Full requirements resolve cleanly under uv + Python 3.10 (185 packages, down from 189; no cu11 packages remain).
  • Docker image builds successfully with torch 2.13.0.
  • A baseline DQL training + eval run completes inside the image (python -m cyberbattle.agents.baseline.run ... --chain_size=4), with torch 2.13.0+cu130 loaded and sensible converging reward curves — confirming the torch 2.13.0 upgrade works for training.

torch 2.13.0 uses the CUDA 13 (cu13) wheel stack, so the explicitly pinned
CUDA 11 packages (nvidia-cublas-cu11, nvidia-cuda-nvrtc-cu11,
nvidia-cuda-runtime-cu11, nvidia-cudnn-cu11) are no longer required by any
dependency and were installed as dead weight. Remove them.

Verified: full requirements resolve (185 packages) and a baseline DQL training
run succeeds in the Docker image with torch 2.13.0.
@blumu
William Blum (blumu) merged commit fe89f9c into main Aug 25, 2026
5 checks passed
@blumu
William Blum (blumu) deleted the wiblum/remove-orphaned-cu11 branch August 25, 2026 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant