where I've copied in the installer OpenCV-4.1.1-dirty-aarch64.sh after saving it from a build with the same l4t image in a different container.
2) running /tmp/OpenCV-4.1.1-dirty-aarch64.sh --prefix=/usr/local/ --skip-license either in bash or during the build for the Dockerfile would move the binaries and lib files into its respective places in /usr/ or /usr/local - I've tried both
3) Finally I ran sudo ldconfig to update the python bindings
What I would expect
4) Running import cv2 in python3 would be successful, instead I get the dreaded segmentation fault error.
So I'm one of those folks trying to use the packaged installer with the magic flag turned on, e.g: https://stackoverflow.com/questions/60081474/install-opencv-from-deb-file-in-docker
What I did: 1) Created a docker container with the following Dockerfile:
where I've copied in the installer
OpenCV-4.1.1-dirty-aarch64.sh
after saving it from a build with the same l4t image in a different container.2) running
/tmp/OpenCV-4.1.1-dirty-aarch64.sh --prefix=/usr/local/ --skip-license
either in bash or during the build for the Dockerfile would move the binaries and lib files into its respective places in/usr/
or/usr/local
- I've tried both3) Finally I ran
sudo ldconfig
to update the python bindingsWhat I would expect 4) Running
import cv2
in python3 would be successful, instead I get the dreaded segmentation fault error.Python Version 3.6.9