-
Notifications
You must be signed in to change notification settings - Fork 3
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
Installation problem when building a docker image #5
Comments
Hello, The
From your CMake messages, I gather the following:
Do you have I suspect the underlying problem is running I'm currently fighting to change the PyPi description to link to this guide. This will make things easier, or at least, less confusing. I noticed you're building on Debian-based distribution. Unfortunately, we don't offer much support for that as we provide for RHEL-based distributions. Any package dependency or building problems you might run into leave you in uncharted territory. Hope this helps! Cheers, [1] https://dmc-docs.web.cern.ch/dmc-docs/gfal2-python/pip-install.html |
Hello, Closing this issue. I believe running the pip-install guide would solve the problem. Unfortunately, the build platform is Debian-based, which is not officially supported. Cheers, |
Thank you, after a while I managed to work again on this issue and at the end following your directions I fixed the issue with the following Dockerfile: FROM almalinux:9
RUN dnf install -y git epel-release
RUN git clone --depth 1 --branch v1.12.2 https://github.com/cern-fts/gfal2-python.git
WORKDIR /gfal2-python/
RUN ./ci/fedora-packages.sh
WORKDIR /gfal2-python/packaging/
RUN RPMBUILD_SRC_EXTRA_FLAGS="--without docs --without python2" make srpm
RUN dnf builddep -y gfal2-python-1.12.2-1.el9.src.rpm
RUN pip install gfal2-python
WORKDIR / Cheers and thank you, |
I'm trying to install gfal2-python in a docker image.
My Dockerfile is the following:
I get the following error:
Any idea why the gfal2.so library is not found? (I tried with python3.9 but I get the same error)
The text was updated successfully, but these errors were encountered: