Repository navigation
Description
❓ Questions and Help
Before proceeding, please note that we recommend
using our discussion forum (https://discuss.dgl.ai) for
general questions. As a result, this issue will
likely be CLOSED shortly.
Dear RFdiffusion / DGL Team,
I am writing to report a persistent issue I'm encountering while trying to set up RFdiffusion on a Linux aarch64 (ARM64) system. I would greatly appreciate any guidance or known solutions.
Problem Description:
When attempting to import RFdiffusion's core modules, I consistently get a ModuleNotFoundError: No module named 'torchdata.datapipes'. This error originates within the dgl library, specifically when it tries to import the datapipes submodule from torchdata.
Environment:
- Operating System: Linux aarch64 (Ubuntu 24.04.1 LTS)
- Python Version: 3.9 (Conda environment)
- PyTorch Version: 2.0.0 (CPU-only build from
conda-forge) - TorchVision Version: 0.15.2
- TorchAudio Version: 2.0.0 (installed via pip)
- CUDA Toolkit: 11.8 (Installed via Conda, but PyTorch build is CPU)
- DGL Version:
conda installattempts for versions 0.8.1, 0.9.1, 1.0.0, 1.1.2 (+cu118) resulted inPackagesNotFoundError(Conda could not find/resolve them).pip install dgl(latest, 2.1.0) successfully installs DGL.
- TorchData Version: 0.11.0 (installed via pip)
- RFdiffusion Source: https://github.com/RosettaCommons/RFdiffusion
- ColabDesign Source: https://github.com/sokrypton/ColabDesign
Steps to Reproduce:
- Switched to a Python 3.9 environment.
- Created a base environment using
conda create -n SE3nv python=3.9. - Installed PyTorch ecosystem (
pytorch==2.0.0,torchvision==0.15.2,cudatoolkit=11.8) fromconda-forge. (This step succeeded.) - Installed DGL latest version (2.1.0) via
pip install dgl. (This step succeeded.) - Installed TorchAudio 2.0.0 via
pip install torchaudio==2.0.0. (This step succeeded.) - Installed
RFdiffusion/env/SE3TransformerandColabDesign(pip install -e .). - Installed remaining pip dependencies (omegaconf, icecream, pyrsistent, matplotlib, ipywidgets, py3Dmol, jupyterlab, etc.).
- Created a base environment using
- Attempted
python -c "from inference.utils import parse_pdb".
Expected Behavior:
RFdiffusion modules should import successfully.
Actual Behavior (Traceback):
(Please copy and paste the full traceback from your most recent ModuleNotFoundError: No module named 'torchdata.datapipes' here. For example:)
Traceback (most recent call last):
File "
Additional Context (What I've Tried):
- Attempted installation in Python 3.10 environment, but failed due to DGL, TorchData, and TorchAudio version conflicts.
- For Python 3.9,
conda installattempts for DGL versions (0.8.1, 0.9.1, 1.0.0, 1.1.2 withcu118label) fromdglteamanddefaultschannels consistently failed withPackagesNotFoundError. This indicates Conda cannot find or resolve theseaarch64builds. - Manually checked
~/miniconda3/envs/SE3nv/lib/python3.9/site-packages/torchdata/vials -land confirmed that thedatapipesdirectory is physically missing. This strongly suggests a structural mismatch between DGL 2.1.0's requirements and the available TorchData 0.11.0 build foraarch64.
Question:
Are there any known working dgl / torchdata version combinations or specific installation instructions for linux-aarch64 that successfully resolve this torchdata.datapipes issue? Are there any official aarch64 Docker images or specific Dockerfile modifications known to work?
Thank you for your time and assistance.
Activity
Gil32610 commentedon Jul 23, 2025
Hey @rudgmleo . I was having the same module not found error for the
torchdata.datapipes.What worked out for me in the current venv and system specs setup was following the installation instructions here: https://www.dgl.ai/pages/start.html
My specs:
venv: Python 3.12.3
pip install dgl -f https://data.dgl.ai/wheels/torch-2.4/cu124/repo.htmlSystem:
CPU:
5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 801 12: 800
Graphics:
renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2
You can adjust your specs accordingly:
schoyeon commentedon Jul 24, 2025
Hello @[Gil32610]
Thank you for your response and for sharing your solution! It's very helpful to know that you encountered the exact same
ModuleNotFoundError: No module named 'torchdata.datapipes'and managed to resolve it. This confirms the root cause of the issue.However, after reviewing your specs and solution, I believe the specific fix you used is unfortunately not directly applicable to my
linux-aarch64(ARM64) system.Reason for non-applicability:
Your
dglinstallation command points to acu124(CUDA 12.4) build of DGL (https://data.dgl.ai/wheels/torch-2.4/cu124/repo.html). This build is specifically compiled forx86_64architectures. My server isaarch64, which means thesex86_64specific builds are incompatible.Upon inspecting
https://data.dgl.ai/wheels/torch-2.4/cpu/foraarch64CPU builds, the availabledglversion is2.1.0(e.g.,dgl-2.1.0-cp39-cp39-manylinux2014_aarch64.whl). As I detailed in my original issue,dgl-2.1.0(when installed onaarch64) still results in theModuleNotFoundError: No module named 'torchdata.datapipes', because thetorchdata==0.11.0package foraarch64physically lacks thedatapipesmodule thatdgl2.1.0 requires.Therefore, the core challenge of finding a compatible
dgl/torchdatabuild forlinux-aarch64that resolves thetorchdata.datapipesissue remains.Do you or anyone else have insights into a working
dgl/torchdatacombination specifically foraarch64?Thank you for your understanding and assistance.
github-actions commentedon Aug 24, 2025
This issue has been automatically marked as stale due to lack of activity. It will be closed if no further activity occurs. Thank you
ramithuh commentedon Sep 9, 2025
I had the same issue with DGL for aarch64, what i ended up doing was building dgl 2.4.0 from source for aarch64 (it was a bit painful).
It looks like dgl 2.4.0 does not depend on torchdata. If you are referring to RFD2 let me know. I installed torch 2.4.0 for aarch64 (CUDA 12.4 as well), so finally i have RFD2 running on this architecture and GPU
github-actions commentedon Oct 11, 2025
This issue has been automatically marked as stale due to lack of activity. It will be closed if no further activity occurs. Thank you
sedfanne commentedon Oct 14, 2025
setting torchdata==0.7.1 is what finally fixed this stuff for me
lll123github commentedon Nov 13, 2025
I have the same problem, with python 3.10 cuda 12.1 pytorch 2.3.1 and torchdata 0.11.0
github-actions commentedon Dec 15, 2025
This issue has been automatically marked as stale due to lack of activity. It will be closed if no further activity occurs. Thank you