Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
CPU only installation looks for CUDA when using mamba
See original GitHub issue😵 Describe the installation problem
Fresh 3.8 Python env
Then
mamba install pytorch torchvision torchaudio cpuonly -c pytorch
mamba install pyg -c pyg -c conda-forge
>>> import torch_geometric
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/zeth/miniconda3/envs/cellvgae/lib/python3.8/site-packages/torch_geometric/__init__.py", line 4, in <module>
import torch_geometric.data
File "/home/zeth/miniconda3/envs/cellvgae/lib/python3.8/site-packages/torch_geometric/data/__init__.py", line 1, in <module>
from .data import Data
File "/home/zeth/miniconda3/envs/cellvgae/lib/python3.8/site-packages/torch_geometric/data/data.py", line 3, in <module>
from torch_geometric.typing import OptTensor, NodeType, EdgeType
File "/home/zeth/miniconda3/envs/cellvgae/lib/python3.8/site-packages/torch_geometric/typing.py", line 4, in <module>
from torch_sparse import SparseTensor
File "/home/zeth/miniconda3/envs/cellvgae/lib/python3.8/site-packages/torch_sparse/__init__.py", line 19, in <module>
torch.ops.load_library(spec.origin)
File "/home/zeth/miniconda3/envs/cellvgae/lib/python3.8/site-packages/torch/_ops.py", line 110, in load_library
ctypes.CDLL(path)
File "/home/zeth/miniconda3/envs/cellvgae/lib/python3.8/ctypes/__init__.py", line 373, in __init__
self._handle = _dlopen(self._name, mode)
OSError: libc10_cuda.so: cannot open shared object file: No such file or directory
Environment
- PyG version: 2.0.3
- PyTorch version: 1.10.2
- OS: Arch Linux
- Python version: 3.8.12
- CUDA/cuDNN version: None
- How you installed PyTorch and PyG (
conda,pip, source): conda <- see above
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
New mamba environment force torch CPU and I don't know why
I tried with version 11.6 and 11.3, nothing changed. This is the command I used: mamba install pytorch torchvision torchaudio -c pytorch -c ......
Read more >GPU enabled TensorFlow builds on conda-forge
Recently we've been able to add GPU-enabled TensorFlow builds to conda-forge! This was quite a journey, with multiple contributors trying ...
Read more >Installation — pytorch_geometric documentation
Ensure that at least PyTorch 1.12.0 is installed: · Find the CUDA version PyTorch was installed with: python -c "import torch; print(torch. ·...
Read more >Getting Started - RAPIDS.ai
In four steps, easily install RAPIDS on a local system or cloud instance with a CUDA enabled GPU for either Conda or Docker...
Read more >Installation - Hugging Face
Install Transformers for whichever deep learning library you're working with, setup your cache, and optionally configure Transformers to run offline.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Interesting. Seems like
mambacannot accurately resolve the existing PyTorch/CUDA environment. Not really sure what to do about this 😦I will open an issue at mamba.