Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] pytorch is not included even though its used by example notebook #74

Closed
tomgreen66 opened this issue Apr 6, 2020 · 1 comment
Closed
Labels
? - Needs Triage Need team to review and classify bug Something isn't working

Comments

@tomgreen66
Copy link

Describe the bug
When using the cusignal notebook from a docker container /rapids/notebooks/cusignal/E2E_Example.ipynb it tries to import torch which is not installed.

Steps/Code to reproduce bug

  1. Run docker container rapidsai_cuda10.1-runtime-centos7 within Singularity.
  2. Start Jupyter server with singularity run --nv rapidsai_cuda10.1-runtime-centos7.sif
  3. Access Jupyter on localhost:8888
  4. Try running the cusignal/E2E_Example.ipynb example.

Expected behavior
Notebook completes without failure.

Environment details (please complete the following information):

  • Environment location: Singularity on local HPC system
  • Method of cuDF install: Docker container
    • If method of install is [Docker], provide docker pull & docker run commands used
      $ singularity pull docker://nvcr.io/nvidia/rapidsai/rapidsai:cuda10.1-runtime-centos7
      $ singularity run --nv rapidsai/rapidsai_cuda10.1-runtime-centos7.sif
  • Please run and attach the output of the cudf/print_env.sh script to gather relevant environment details

rapids.log

Additional context
Using Singularity on HPC so could be issues with that.

@ajschmidt8
Copy link
Member

ajschmidt8 commented Sep 28, 2020

@tomgreen66, thanks for bringing this to our attention and apologies for the late reply here. I'm told that we intentionally exclude PyTorch from our images due to its size. However, I just opened a PR to cusignal (rapidsai/cusignal#242) to add both an explanation and a workaround for users who are running this Notebook in our containers. Please see that PR for more details.

closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
? - Needs Triage Need team to review and classify bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants