Hi all, I pulled dolfinx in WSL2 and tried to import dolfinx. It reported “IIIegal instruction”.
To be able to help you with this, I would have to have some more information. First, could you start the newly pulled docker image?
Secondly, could you give me the full terminal print out of what you called to get this error, for instance, what happens if you call:
python3 -c "import dolfinx"
Hi dokken, the output is:
Windows Terminal
wws@wws-PC:/mnt/e/Worksapce/fenics$ sudo docker run -ti -v $(pwd):/home/fenics/shared -w /home/fenics/shared/ --rm dolfi
nx/complex
root@49a0f1ba5470:/home/fenics/shared# python3
Python 3.7.5 (default, Nov 20 2019, 09:21:52)
[GCC 9.2.1 20191008] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import dolfinx
Illegal instruction
root@49a0f1ba5470:/home/fenics/shared# ipython
Python 3.7.5 (default, Nov 20 2019, 09:21:52)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.13.0 -- An enhanced Interactive Python. Type '?' for help.
Before today, when was the last time you pulled the docker image? There hasnt been many changes to the Dockerfile in the last weeks, so Im having issues pointing to a specific change that can have caused this.
Hi, dokken. I pulled the image today in another computer under linux subsystem on windows. I never pulled images on this computer before.
To me it seems like an issue with the computer you are using. See for instance: https://discuss.mxnet.io/t/illegal-instruction-python3-6-and-mxnet-1-4/3418/9.
dokken, is there a detailed specification on how to compile the dolfinx complex version from source under Ubuntu 18.04?
The Dockerfile is a line by line instruction on how to install dolfinx on ubuntu 19.04 (with sudo privileges).
So in theory you could follow this line by line.
However, I would first test if you can run the old docker images in your docker container (like quay.io/repository/fenicsproject/stable) to see if there is an issue with docker or dolfinx.
dokken, your last link is dolfin and I can import it
What I can then suggest is that you use the Dockerfile link above, build the image on your computer using docker build
, and go backwards in the docker history until you hit the commit that doesnt work for you. Then we can look at the changes in between the images and see if there is an easy fix.