ImportError: libcblas.so.3: cannot open shared object file: No such file or directory #47
Comments
|
Which platform are you using?
There are unfortunately some known issues with the docker containers on
some platforms at the moment. I believe @snh was looking into it.
…On Tue, 15 Nov 2022, 08:29 on8pz, ***@***.***> wrote:
Looks like the latest docker image does not start. It shows the following
error and keeps restarting:
`Traceback (most recent call last):
File "/root/.local/lib/python3.9/site-packages/numpy/core/*init*.py",
line 23, in
from . import multiarray
File "/root/.local/lib/python3.9/site-packages/numpy/core/multiarray.py",
line 10, in
from . import overrides
File "/root/.local/lib/python3.9/site-packages/numpy/core/overrides.py",
line 6, in
from numpy.core._multiarray_umath import (
ImportError: libcblas.so.3: cannot open shared object file: No such file
or directory
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/chasemapper/horusmapper.py", line 30, in
from chasemapper.geometry import *
File "/opt/chasemapper/chasemapper/geometry.py", line 10, in
import numpy as np
File "/root/.local/lib/python3.9/site-packages/numpy/*init*.py", line
140, in
from . import core
File "/root/.local/lib/python3.9/site-packages/numpy/core/*init*.py",
line 49, in
raise ImportError(msg)
ImportError:
IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
Importing the numpy C-extensions failed. This error can happen for
many reasons, often due to issues with your setup or how NumPy was
installed.
We have compiled some common reasons and troubleshooting tips at:
https://numpy.org/devdocs/user/troubleshooting-importerror.html
Please note and check the following:
- The Python version is: Python3.9 from "/usr/local/bin/python3"
- The NumPy version is: "1.23.3"
and make sure that they are the versions you expect.
Please carefully study the documentation linked above for further help.
Original error was: libcblas.so.3: cannot open shared object file: No such
file or directory
`
***@***.***:/data/chasemapper$ docker pull
ghcr.io/projecthorus/chasemapper:latest latest: Pulling from
projecthorus/chasemapper Digest:
sha256:22bfb103c98180fdc91a31bc97a3577564370a1ce7065bbf54c59e951bb9a1f0
Status: Image is up to date for ghcr.io/projecthorus/chasemapper:latest
ghcr.io/projecthorus/chasemapper:latest
—
Reply to this email directly, view it on GitHub
<#47>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAH57E3IKEDAQJTQTRO45QLWIKY3DANCNFSM6AAAAAASAI47VQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
|
Sorry I should have said what architecture. E.g. x64, arm of some kind, etc.
The amd64 build is definitely broken.
…On Tue, 15 Nov 2022, 08:32 on8pz, ***@***.***> wrote:
***@***.***:/data/chasemapper$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
—
Reply to this email directly, view it on GitHub
<#47 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAH57E2ARCEK7QT7I56GW23WIKZGDANCNFSM6AAAAAASAI47VQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I guess I'm out of luck then ? |
|
Until it gets fixed :-) You can also do a 'native' install, which is a bit more involved: https://github.com/projecthorus/chasemapper#local-install---dependencies |
|
FYI, all it took to fix was a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looks like the latest docker image does not start. It shows the following error and keeps restarting:
The text was updated successfully, but these errors were encountered: