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] ImportError: libgdal.so.26: cannot open shared object file: No such file or directory in nightly container #275

Closed
drabastomek opened this issue Aug 23, 2020 · 8 comments
Labels
bug Something isn't working Needs Triage Need team to review and classify

Comments

@drabastomek
Copy link

Describe the bug
When importing cuspatial I got this ImportError: libgdal.so.26: cannot open shared object file: No such file or directory in nightly container�.

FULL TRACE

---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-3-aa33e033382d> in <module>
      1 import cudf
----> 2 import cuspatial
      3 from collections import OrderedDict
      4 import numpy as np
      5 import datetime as dt

/opt/conda/envs/rapids/lib/python3.7/site-packages/cuspatial/__init__.py in <module>
----> 1 from .core import interpolate
      2 from .core.gis import (
      3     directed_hausdorff_distance,
      4     haversine_distance,
      5     lonlat_to_cartesian,

/opt/conda/envs/rapids/lib/python3.7/site-packages/cuspatial/core/interpolate.py in <module>
      6 from cudf import DataFrame, Series
      7 
----> 8 from cuspatial._lib.interpolate import (
      9     cubicspline_coefficients,
     10     cubicspline_interpolate,

ImportError: libgdal.so.26: cannot open shared object file: No such file or directory

Steps/Code to reproduce bug
import cuspatial should load the library.

Expected behavior
Should load the library.

Environment details (please complete the following information):

  • Environment location: Docker

  • Method of cuSpatial install: Docker

    • If method of install is [Docker], provide docker pull & docker run commands used

    -- PULL: docker pull rapidsai/rapidsai-nightly:cuda10.2-runtime-ubuntu18.04-py3.7
    -- RUN:

docker run --gpus all -it -p 8888:8888 -p 8787:8787 -p 8786:8786 --name kdd_rapids \
	rapidsai/rapidsai-nightly:cuda10.2-runtime-ubuntu18.04-py3.7

Additional context
Add any other context about the problem here.

@drabastomek drabastomek added Needs Triage Need team to review and classify bug Something isn't working labels Aug 23, 2020
@cwharris
Copy link
Contributor

Hi @drabastomek, what version of gdal is currently installed in the container?

@thomcom
Copy link
Contributor

thomcom commented Aug 25, 2020

Looks like it is gdal 3.1.2 @cwharris

@drabastomek
Copy link
Author

As @thomcom suggested -- current version is GDAL 3.1.2, released 2020/07/07.

The workaround that got me unblocked involved commenting out portions of the __init__.py and also copying the libdgal.so.27 to libgdal.so.26 (I only needed the haversine_distance so that was fine).

@github-actions
Copy link

This issue has been marked rotten due to no recent activity in the past 90d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

@github-actions
Copy link

This issue has been marked stale due to no recent activity in the past 30d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be marked rotten if there is no activity in the next 60d.

@github-actions github-actions bot added the stale label Feb 16, 2021
@trxcllnt
Copy link
Contributor

trxcllnt commented Apr 9, 2021

I think this was the same issue we filed #375 to fix?

@github-actions
Copy link

github-actions bot commented May 9, 2021

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

@harrism
Copy link
Member

harrism commented May 10, 2021

Closing due to inactivity. Please reopen if still needed.

@harrism harrism closed this as completed May 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Needs Triage Need team to review and classify
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants